Service disruption via slave-pointer registration race
Published Aug 28, 2026 · Updated Aug 28, 2026
Race condition in the Linux IMX I2C driver allows attackers to disrupt slave registration or crash affected systems. The i2c_imx_reg_slave function stored a slave pointer before runtime resume succeeded, and an unlocked error-path update raced with dereferencing by the shared-IRQ handler under slave_lock. Exploitation requires IMX I2C slave mode, a runtime-resume failure, and concurrent interrupt handling, resulting in persistent EBUSY registration failures or a NULL-pointer kernel crash.
Summary
What happened
Race condition in the Linux IMX I2C driver allows attackers to disrupt slave registration or crash affected systems. The i2c_imx_reg_slave function stored a slave pointer before runtime resume succeeded, and an unlocked error-path update raced with dereferencing by the shared-IRQ handler under slave_lock. Exploitation requires IMX I2C slave mode, a runtime-resume failure, and concurrent interrupt handling, resulting in persistent EBUSY registration failures or a NULL-pointer kernel crash.
The record
- CVE
- CVE-2026-80678
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.11
- Affected versionversion=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <12a4f0950a158d98552cbaeacc35edccd8d975fa
- Affected versionversion=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <614ca6594e301ff682999797c2216e9685558a2b
- Affected versionversion=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <754bc62f72fd64b202462367134ac8ce95b005de
- Affected versionversion=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <b9f6f4883b9ac86654e75899d0dbf8a7a96ad5d8
- Affected versionversion=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <cfdf6e13518589f911b7eace6ccb788e4ed87397
- Affected versionversion=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <d64ec362c369bbc33833f7936d5f3a706b0d5c45
- Affected versionversion=f7414cd6923fd7f78e57086fc964ba2dc25db5c1 <d6748f6802f3eebafaa16a5e5dcfbfb9b3bc173f
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo