CVE-2026-80894: iommufd: Fix wrong hwpt passed to iommufd_auto_response_faults on replace
Noroxi assessment
Priority: Monitor (action score 0/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.16% (FIRST EPSS).
- Fixed version: Linux Linux 564ac339c0f8bada4e77a57a92bab9d3df635e07, 6.12.105, 6.14.
Low priority for now. Upgrade to Linux Linux 564ac339c0f8bada4e77a57a92bab9d3df635e07, 6.12.105, 6.14 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: iommufd: Fix wrong hwpt passed to iommufd_auto_response_faults on replace iommufd_hwpt_replace_device() calls: iommufd_auto_response_faults(hwpt, old_handle); passing the *new* hwpt together with the handle of the device's *old* domain. This should be a parameter mismatch: 1. Semantically, iommufd_auto_response_faults(x, handle) scans x->fault's deliver list and response xarray for groups matching "handle". A group is queued under the hwpt that was attached at fault-delivery time. old_handle is fetched *before* the domain switch, so its group lives on old->fault, not on the new hwpt->fault. 2. Historically, the first argument was "old". The routine was introduced by commit b7d8833677ba ("iommufd: Fault-capable hwpt attach/detach/replace") as __fault_domain_replace_dev() in fault.c, correctly calling iommufd_auto_response_faults(old, curr). Commit fb21b1568ada ("iommufd: Make attach_handle generic than fault specific") moved this into iommufd_hwpt_replace_device() in device.c and swapped it to "hwpt". This should be a refactor regression, not an intentional change. Fix this by passing "old" instead.
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
- 1e0216b6a58c79b5ee91c78706d5f560e4d1f56f, 4b23c4b991eb90cc7bca42e9f81142feedd4bb56, 6.15affected
- 6d11543bf37abdf60b8e6022a62fccfb82a5fe2e and later · before adb87155b67f9759ff010c0a99559f5bffa45dcfaffected · git
- fb21b1568adaa76af7a8c853f37c60fba8b28661 and later · before 564ac339c0f8bada4e77a57a92bab9d3df635e07affected · git
- fb21b1568adaa76af7a8c853f37c60fba8b28661 and later · before 8eb077025279304268bd58657f0af3d388822b21affected · git
- fb21b1568adaa76af7a8c853f37c60fba8b28661 and later · before ba5c0f28a26e7d9be1e0997f8920dd638e2782fdaffected · git
- 6.12.24 and later · before 6.12.105affected · semver
- 6.13.12 and later · before 6.14affected · semver
- 6.14.3 and later · before 6.15affected · semver
- before 6.15not affected · semver
- 6.12.105 and later · up to and including 6.12.*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-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-80892Sep 4, 2026 · erofs: cap LZMA stream pool size0Monitor
- ← EarlierCVE-2026-80893Sep 4, 2026 · mm/hugetlb: fix swap entry corruption when clearing uffd-wp at fork()0Monitor
- Later →CVE-2026-80895Sep 4, 2026 · mshv: Order pt_vp_array publish against irqfd assertion path0Monitor
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 | 564ac339c0f8bada4e77a57a92bab9d3df635e07 | Vendor (CNA) |
| Linux Linux | 6.12.105 | Vendor (CNA) |
| Linux Linux | 6.14 | Vendor (CNA) |
| Linux Linux | 6.15 | Vendor (CNA) |
| Linux Linux | 8eb077025279304268bd58657f0af3d388822b21 | Vendor (CNA) |
| Linux Linux | adb87155b67f9759ff010c0a99559f5bffa45dcf | Vendor (CNA) |
| Linux Linux | ba5c0f28a26e7d9be1e0997f8920dd638e2782fd | Vendor (CNA) |
| debian:linux | 6.12.105-1 · Debian:13 | 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).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.