CVE-2026-80894iommufd: Fix wrong hwpt passed to iommufd_auto_response_faults on replace
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 9 days later
· 9 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 6d11543bf37abdf60b8e6022a62fccfb82a5fe2e – < adb87155b67f9759ff010c0a99559f5bffa45dcf
- affected fb21b1568adaa76af7a8c853f37c60fba8b28661 – < 564ac339c0f8bada4e77a57a92bab9d3df635e07
- affected fb21b1568adaa76af7a8c853f37c60fba8b28661 – < 8eb077025279304268bd58657f0af3d388822b21
- affected fb21b1568adaa76af7a8c853f37c60fba8b28661 – < ba5c0f28a26e7d9be1e0997f8920dd638e2782fd
- affected 1e0216b6a58c79b5ee91c78706d5f560e4d1f56f
- affected 4b23c4b991eb90cc7bca42e9f81142feedd4bb56
- affected 6.12.24 – < 6.12.105
- affected 6.13.12 – < 6.14
- affected 6.14.3 – < 6.15
- affected 6.15
- unaffected < 6.15
- unaffected 6.12.105 – ≤ 6.12.*
- unaffected 6.18.44 – ≤ 6.18.*
- unaffected 7.1.8 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/adb87155b67f9759ff010c0a99559f5bffa45dcf (opens in a new tab)
- https://git.kernel.org/stable/c/564ac339c0f8bada4e77a57a92bab9d3df635e07 (opens in a new tab)
- https://git.kernel.org/stable/c/8eb077025279304268bd58657f0af3d388822b21 (opens in a new tab)
- https://git.kernel.org/stable/c/ba5c0f28a26e7d9be1e0997f8920dd638e2782fd (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-71644 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80894)Record last updated .