In the Linux kernel i.MX I2C driver, performing a SMBus block-read with a byte count of zero can cause the I²C bus to become permanently locked. This issue is an example of CWE-413, improper state machine control. The driver’s interrupt‑driven state machine fails to issue a STOP condition, leaving the target device holding the data line (SDA) and preventing any further communication on that bus. This can render I²C‑connected peripherals inoperable and disrupt system components that depend on them.

The flaw exists in Linux kernels that include the imx I²C driver without the fix committed in 07fd9385f0d87dff4b34f355f68adf701080cb24. The affected code is part of the v6.13 state‑machine rework; prior regressions also exist in the v3.16 path. Systems that run these kernels on i.MX hardware and perform SMBus block-read operations are potentially impacted.

The CVSS score of 7.5 coupled with an EPSS score of less than 1% indicates moderate severity but low probability of exploitation. The vulnerability is not catalogued in CISA KEV. Exploitation would require an attacker to trigger a block-read with a zero byte count, which typically implies local privileged access or control over code that performs the SMBus operation; this requirement is inferred and not explicitly stated in the advisory. While the vulnerability cannot be used for code execution or data exfiltration, it can cause a denial of service that affects system availability and reliability. The weakness is classified as CWE-413, improper state machine control.