CVE-2026-80678

i2c: imx: Fix slave registration race and error handling

HIGH
8.4
CVSS Score
Published: August 28, 2026 at 06:52 AM UTC
Updated: October 16, 2026 at 08:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.4
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11f7414cd6923fd7f78e57086fc964ba2dc25db5c1
Vendor states this is fixed in 12a4f0950a158d98552cbaeacc35edccd8d975fa (fixed)
Vendor states this is fixed in 614ca6594e301ff682999797c2216e9685558a2b (fixed)
Vendor states this is fixed in 754bc62f72fd64b202462367134ac8ce95b005de (fixed)
Vendor states this is fixed in b9f6f4883b9ac86654e75899d0dbf8a7a96ad5d8 (fixed)
Vendor states this is fixed in cfdf6e13518589f911b7eace6ccb788e4ed87397 (fixed)
Vendor states this is fixed in d64ec362c369bbc33833f7936d5f3a706b0d5c45 (fixed)
Vendor states this is fixed in d6748f6802f3eebafaa16a5e5dcfbfb9b3bc173f (fixed)
Vendor states this is fixed in 5.11 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.4HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card