CVE-2026-80678: i2c: imx: Fix slave registration race and error handling
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 12a4f0950a158d98552cbaeacc35edccd8d975fa, 614ca6594e301ff682999797c2216e9685558a2b, 754bc62f72fd64b202462367134ac8ce95b005de; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 12a4f0950a158d98552cbaeacc35edccd8d975fa, 614ca6594e301ff682999797c2216e9685558a2b, 754bc62f72fd64b202462367134ac8ce95b005de; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 28, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.11affected
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before 754bc62f72fd64b202462367134ac8ce95b005deaffected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before cfdf6e13518589f911b7eace6ccb788e4ed87397affected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before b9f6f4883b9ac86654e75899d0dbf8a7a96ad5d8affected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before d6748f6802f3eebafaa16a5e5dcfbfb9b3bc173faffected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before 12a4f0950a158d98552cbaeacc35edccd8d975faaffected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before 614ca6594e301ff682999797c2216e9685558a2baffected · git
- f7414cd6923fd7f78e57086fc964ba2dc25db5c1 and later · before d64ec362c369bbc33833f7936d5f3a706b0d5c45affected · git
- before 5.11not affected · semver
- 5.15.217 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80676Aug 28, 2026 · Drivers: hv: vmbus: use generic driver_override infrastructure0Monitor
- ← EarlierCVE-2026-80677Aug 28, 2026 · driver core: use READ_ONCE() for dev->driver in dev_has_sync_state()31Monitor
- Later →CVE-2026-80681Aug 28, 2026 · vxlan: re-fetch eth header after route_shortcircuit()39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 12a4f0950a158d98552cbaeacc35edccd8d975fa | Vendor (CNA) |
| Linux Linux | 614ca6594e301ff682999797c2216e9685558a2b | Vendor (CNA) |
| Linux Linux | 754bc62f72fd64b202462367134ac8ce95b005de | Vendor (CNA) |
| Linux Linux | b9f6f4883b9ac86654e75899d0dbf8a7a96ad5d8 | Vendor (CNA) |
| Linux Linux | cfdf6e13518589f911b7eace6ccb788e4ed87397 | Vendor (CNA) |
| Linux Linux | d64ec362c369bbc33833f7936d5f3a706b0d5c45 | Vendor (CNA) |
| Linux Linux | d6748f6802f3eebafaa16a5e5dcfbfb9b3bc173f | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/614ca6594e301ff682999797c2216e9685558a2b
- git.kernel.org/stable/c/754bc62f72fd64b202462367134ac8ce95b005de
- git.kernel.org/stable/c/b9f6f4883b9ac86654e75899d0dbf8a7a96ad5d8
- git.kernel.org/stable/c/cfdf6e13518589f911b7eace6ccb788e4ed87397
- git.kernel.org/stable/c/d64ec362c369bbc33833f7936d5f3a706b0d5c45
- git.kernel.org/stable/c/d6748f6802f3eebafaa16a5e5dcfbfb9b3bc173f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.