CVE-2026-80678

HIGHCVSS 8.4/10EPSS 0.17%

Last modified

CVE-2026-80678 is a high-severity vulnerability rated 8.4/10 on the CVSS scale. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
0.17%

6.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= f7414cd6923fd7f78e57086fc964ba2dc25db5c1, < 754bc62f72fd64b202462367134ac8ce95b005de; >= f7414cd6923fd7f78e57086fc964ba2dc25db5c1, < cfdf6e13518589f911b7eace6ccb788e4ed87397; >= f7414cd6923fd7f78e57086fc964ba2dc25db5c1, < b9f6f4883b9ac86654e75899d0dbf8a7a96ad5d8; >= f7414cd6923fd7f78e57086fc964ba2dc25db5c1, < d6748f6802f3eebafaa16a5e5dcfbfb9b3bc173f; >= f7414cd6923fd7f78e57086fc964ba2dc25db5c1, < 12a4f0950a158d98552cbaeacc35edccd8d975fa; >= f7414cd6923fd7f78e57086fc964ba2dc25db5c1, < 614ca6594e301ff682999797c2216e9685558a2b; >= f7414cd6923fd7f78e57086fc964ba2dc25db5c1, < d64ec362c369bbc33833f7936d5f3a706b0d5c45
LinuxLinux5.11

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80678?
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.
How severe is CVE-2026-80678?
CVE-2026-80678 has a CVSS score of 8.4/10 (HIGH severity). The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-80678?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-80678?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST