The Linux kernel’s i2c_imx driver contains a race condition and a null pointer dereference that can lead to a denial of service. During slave registration, the driver assigns the slave pointer before successfully resuming power management. If the resume fails, the slave pointer is left non‑NULL and subsequent registrations fail with –EBUSY. Concurrent execution of the shared IRQ handler can also dereference the stale pointer while holding the slave_lock, potentially causing a crash. Fixing the race condition and ensuring the pointer is cleared on failure eliminates the possibility of a stale pointer and prevents the crash, thereby restoring reliable operation of the I2C controller.

Any Linux kernel installation that includes the i2c_imx driver is potentially affected, including all i.MX platforms that rely on this I2C controller driver. The patch is applied at the kernel level, so all kernel versions prior to the commit in the linked revisions are considered vulnerable. No specific release numbers are listed, but any kernel build that contains the unpatched i2c_imx implementation is at risk.

The vulnerability is local and requires that an attacker can trigger I2C slave registration or interrupt handling. The lack of an EPSS score and absence from the CISA KEV catalog suggest that it is not a known exploited vulnerability, but the timing nature and local scope could allow denial of service or disruption of I2C devices on the affected system. The CVSS score is not provided; however, the impact is a denial of service due to possible device registration failure or driver crash.