i2c: imx-lpi2c: mark I2C adapter when hardware is powered down
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.397.1.47.2In 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.
From the CVE record · Linux
On some i.MX platforms, the Linux kernel’s imx-lpi2c driver may access I2C registers during suspend or resume while the controller’s resources are unavailable, causing a system hang. This can occur when an I2C client’s periodic workqueue triggers a transfer in that window; the input does not describe an attacker route or authentication requirement.
Engineers running Linux on i.MX platforms using imx-lpi2c should check their kernel; affected versions are not specified.