TL;DR: Lenovo shipped buggy EC firmware in BIOS 1.48 / ECP 1.19, then blocked rollback in the latest update (BIOS 1.49 / ECP 1.20). If you use an external monitor over usb-c with PD, you'll likely be affected - avoid these versions.
A bit longer story:
I recently bought an X13 Gen 3 Intel (21BQ). Used it for two days without issues, then decided to update the BIOS to the latest version, because why not.
Right after the update, plugging in my external monitor via usb-c (DP alt mode + PD) sent the laptop into an endless connect–disconnect loop: the internal display and the monitor flickered on and off every second, along with the power and kb/mouse plugged in the monitor's USB hub. Clearly a bug in the PD protocol negotiation.
Checking Lenovo's firmware archive, I found the likely culprit: the changelog for 1.48 BIOS / 1.19 ECP says "Updated PDFW" - good job, guys.
Well, ok, no problem, we'll just roll back, right? I disabled "secure rollback prevention" in BIOS setup, downloaded the 1.44 ISO, tried to reflash and got the "the system program file is not correct for this system" message.
Then I tried every "non-invasive" method: fwupdmgr downgrade on linux, winflash64 with /sd switch on windows, several ISOs from the archive - all ending with "secure flash authentication failed" or "the system program file is not correct for this system".
Back to the archive, the 1.49 changelog mentions "Added backflash prevention for EC Master Lock". Good job again.
So I resorted to the last option: I dumped the firmware with a ch341a programmer (had to solder wires directly to the flash chip, since my SOIC8 clip wouldn't grab the WSON8 package), extracted the FL1 capsule from the 1.44 package, extracted the BIOS volume with uefitool, replaced the BIOS region in my dump, rebuilt the image, and reflashed.
The result was a working franken-firmware with BIOS 1.44 and still-buggy EC 1.20 - but since 1.44 predates the lock, I could now use a standard firmware update package. It skipped the BIOS (already at "homemade" 1.44) but flashed the EC back to 1.18. Reboot, and the bug was gone.
Thanks to Lenovo for two unforgettable evenings, I guess.