CVE-2026-80680: i2c: amd-mp2: Unregister callback on adapter add failure
Noroxi assessment
Priority: Monitor (action score 31/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.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1883a09a37fed497b9efacf736c23624a472246b, 2f7789b3a9628819ebf90bcba8f9da3c139f8687, 4786d4d70dcd1e6b7e044f2348e00f201947b69c; 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 1883a09a37fed497b9efacf736c23624a472246b, 2f7789b3a9628819ebf90bcba8f9da3c139f8687, 4786d4d70dcd1e6b7e044f2348e00f201947b69c; 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: amd-mp2: Unregister callback on adapter add failure amd_mp2_register_cb() stores the platform I2C context in the MP2 PCI driver's callback table before the adapter is registered. If i2c_add_adapter() fails, probe returns and devres frees the context, but the PCI driver can still dereference the stale pointer from its IRQ and system-sleep callbacks. Unregister the callback before returning the adapter registration error.
- Published
- Aug 28, 2026
- Updated
- Aug 29, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- 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.2affected
- 529766e0a0114438887382a68d97341fbf8349fb and later · before 9142a3dcff0d80a3a24ce159aee19ddc869d9784affected · git
- 529766e0a0114438887382a68d97341fbf8349fb and later · before 2f7789b3a9628819ebf90bcba8f9da3c139f8687affected · git
- 529766e0a0114438887382a68d97341fbf8349fb and later · before 4786d4d70dcd1e6b7e044f2348e00f201947b69caffected · git
- 529766e0a0114438887382a68d97341fbf8349fb and later · before b7c2c5c8868737926410b93d1223ada17625ead3affected · git
- 529766e0a0114438887382a68d97341fbf8349fb and later · before cf107c5983dc70fcf932a305581a5f976d908ff1affected · git
- 529766e0a0114438887382a68d97341fbf8349fb and later · before 1883a09a37fed497b9efacf736c23624a472246baffected · git
- 529766e0a0114438887382a68d97341fbf8349fb and later · before 8bf719659406e4a1b56d441e0c7da2085d891d96affected · git
- 529766e0a0114438887382a68d97341fbf8349fb and later · before 82048795242f04275a3f49ffc66ad851b6120954affected · git
- before 5.2not 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-80675Aug 28, 2026 · libbpf: Reject non-exclusive metadata maps in the signed loader28Monitor
- ← EarlierCVE-2026-80679Aug 28, 2026 · s390/dasd: Fix potential NULL pointer dereference0Monitor
- Later →CVE-2026-80682Aug 28, 2026 · riscv/mm: use physical alignment for vmemmap_start_pfn31Monitor
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 | 1883a09a37fed497b9efacf736c23624a472246b | Vendor (CNA) |
| Linux Linux | 2f7789b3a9628819ebf90bcba8f9da3c139f8687 | Vendor (CNA) |
| Linux Linux | 4786d4d70dcd1e6b7e044f2348e00f201947b69c | Vendor (CNA) |
| Linux Linux | 82048795242f04275a3f49ffc66ad851b6120954 | Vendor (CNA) |
| Linux Linux | 8bf719659406e4a1b56d441e0c7da2085d891d96 | Vendor (CNA) |
| Linux Linux | 9142a3dcff0d80a3a24ce159aee19ddc869d9784 | Vendor (CNA) |
| Linux Linux | b7c2c5c8868737926410b93d1223ada17625ead3 | Vendor (CNA) |
| Linux Linux | cf107c5983dc70fcf932a305581a5f976d908ff1 | 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.
- A low-privileged account is enough.
- 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
- Low
- 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:L/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2f7789b3a9628819ebf90bcba8f9da3c139f8687
- git.kernel.org/stable/c/4786d4d70dcd1e6b7e044f2348e00f201947b69c
- git.kernel.org/stable/c/82048795242f04275a3f49ffc66ad851b6120954
- git.kernel.org/stable/c/8bf719659406e4a1b56d441e0c7da2085d891d96
- git.kernel.org/stable/c/9142a3dcff0d80a3a24ce159aee19ddc869d9784
- git.kernel.org/stable/c/b7c2c5c8868737926410b93d1223ada17625ead3
- git.kernel.org/stable/c/cf107c5983dc70fcf932a305581a5f976d908ff1
Vendor advisories and official records. Exploit/PoC links are deliberately left out.