i2c: imx: Fix slave registration race and error handling
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel d6748f6802f3eebafaa16a5e5dcfbfb9b3bc173f, Kernel 12a4f0950a158d98552cbaeacc35edccd8d975fa, Kernel 614ca6594e301ff682999797c2216e9685558a2b and 10 more.
In the Linux kernel, the following vulnerability has been resolved: i2c: imx: Fix slave registration race and error handling In i2c_imx_reg_slave(), the slave pointer was assigned before pm_runtime_resume_and_get(). If pm_runtime_resume_and_get() failed, the error path returned without clearing i2c_imx->slave, leaving it non-NULL and causing all subsequent registration attempts to fail with -EBUSY. Additionally, because this driver uses a shared IRQ, the interrupt handler i2c_imx_isr() can execute concurrently and, after acquiring slave_lock, dereference i2c_imx->slave. The previous fix attempt added a lockless i2c_imx->slave = NULL on the error path, but that could race with the ISR under the lock and still cause a NULL pointer dereference. Fix both issues by deferring the assignment of i2c_imx->slave and i2c_imx->last_slave_event to after a successful resume, and by performing the assignment inside the slave_lock critical section. This guarantees that the slave pointer is never left stale on the error path and is always valid when observed by the interrupt handler.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <d6748f6802f3eebafaa16a5e5dcfbfb9b3bc173f, >=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <12a4f0950a158d98552cbaeacc35edccd8d975fa, >=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <614ca6594e301ff682999797c2216e9685558a2b, >=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <754bc62f72fd64b202462367134ac8ce95b005de, >=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <b9f6f4883b9ac86654e75899d0dbf8a7a96ad5d8, >=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <cfdf6e13518589f911b7eace6ccb788e4ed87397, >=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <d64ec362c369bbc33833f7936d5f3a706b0d5c45, =5.11 | d6748f6802f3eebafaa16a5e5dcfbfb9b3bc173f, 12a4f0950a158d98552cbaeacc35edccd8d975fa, 614ca6594e301ff682999797c2216e9685558a2b, 754bc62f72fd64b202462367134ac8ce95b005de, b9f6f4883b9ac86654e75899d0dbf8a7a96ad5d8, cfdf6e13518589f911b7eace6ccb788e4ed87397, d64ec362c369bbc33833f7936d5f3a706b0d5c45 |
| linux-kernel: Kernel | >=5.16.0 <6.1.183, >=6.13.0 <6.18.44, >=6.19.0 <7.1.8, >=6.2.0 <6.6.151, >=6.7.0 <6.12.103, >=5.11.0 <5.15.217 | 6.1.183, 6.18.44, 7.1.8, 6.6.151, 6.12.103, 5.15.217 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket