The imx‑lpi2c driver on some i.MX platforms schedules periodic work that can trigger I²C transfers while the system is in a no‑IRQ suspend or resume state. During this narrow window the controller’s clock and pin‑control resources may already be disabled or not yet restored. The driver therefore attempts to read or write I²C registers when the hardware is unavailable, which can cause the entire system to lock up. This flaw results in a loss of availability; normal operation cannot resume until the system is rebooted or otherwise recovered. The weakness corresponds to missing safeguards around hardware power state checks, as captured by CWE‑820.

Linux kernel installations that include the imx‑lpi2c I²C driver are affected. The vulnerability is present in any kernel version before the commit that marks the adapter as suspended and blocks new transfers during no‑IRQ suspend. All i.MX hardware that relies on this driver is potentially impacted, regardless of vendor or device tree configuration. No specific downstream patches are listed, so users should verify whether their kernel contains the fix commit.

The EPSS score of less than 1% indicates a very low probability of exploitation as of the current analysis. The issue is not recorded in the CISA KEV catalog. Likely exploitation would require a local or privileged attacker to manipulate the system’s suspend/resume cycle while periodic work continues, making it a limited attack surface. However, because the impact is a complete system hang, the risk to availability is significant for any device that experiences the fault. The CVSS score of 5.5 suggests a moderate severity, which balances the moderate risk of exploitation with the severe operational impact of a system lock‑up.