In the Linux kernel, the following vulnerability has been resolved: i2c: imx-lpi2c: mark I2C adapter when hardware is powered down On some i.MX platforms, certain I2C client drivers keep a periodic workqueue which continues to trigger I2C transfers. During system suspend/resume, there exists a time window between: - suspend_noirq and the system entering suspend - the system starting to resume and resume_noirq In this window, the I2C controller resources such as clock and pinctrl may already be disabled or not yet restored. If a workqueue triggers an I2C transfer in this period, the driver attempts to access I2C registers while the hardware resources are unavailable, which may lead to system hang. Mark the I2C adapter as suspended during noirq suspend and block new transfers until resume, ensuring that I2C transfers are only issued when hardware resources are available.

A flaw was found in the Linux kernel's i2c: imx-lpi2c driver. During system suspend and resume operations, certain I2C client drivers may attempt to perform I2C transfers while the underlying hardware resources are temporarily unavailable. This can occur because the I2C adapter is not properly marked as suspended, allowing transfers to be initiated at an inappropriate time. The consequence of this vulnerability is a system hang, which can lead to a denial of service.

Red Hat Enterprise Linux 10 Not affected kernel Red Hat Enterprise Linux 6 Not affected kernel Red Hat Enterprise Linux 7 Not affected kernel Red Hat Enterprise Linux 7 Not affected kernel-rt Red Hat Enterprise Linux 8 Not affected kernel Red Hat Enterprise Linux 8 Not affected kernel-rt Red Hat Enterprise Linux 9 Not affected kernel Red Hat Enterprise Linux 9 Not affected kernel-rt https://www.cve.org/CVERecord?id=CVE-2026-64278 https://nvd.nist.gov/vuln/detail/CVE-2026-64278 https://lore.kernel.org/linux-cve-announce/2026072501-CVE-2026-64278-9f7c@gregkh/T