Answer in brief
CVE-2026-80894 records a Unknown severity vulnerability in iommufd: Fix wrong hwpt passed to iommufd_auto_response_faults on replace. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6d11543bf37abdf60b8e6022a62fccfb82a5fe2e <adb87155b67f9759ff010c0a99559f5bffa45dcf || >=fb21b1568adaa76af7a8c853f37c60fba8b28661 <564ac339c0f8bada4e77a57a92bab9d3df635e07 || >=fb21b1568adaa76af7a8c853f37c60fba8b28661 <8eb077025279304268bd58657f0af3d388822b21 || >=fb21b1568adaa76af7a8c853f37c60fba8b28661 <ba5c0f28a26e7d9be1e0997f8920dd638e2782fd || 1e0216b6a58c79b5ee91c78706d5f560e4d1f56f || 4b23c4b991eb90cc7bca42e9f81142feedd4bb56 || >=6.12.24 <6.12.105 || >=6.13.12 <6.14 || >=6.14.3 <6.15 | adb87155b67f9759ff010c0a99559f5bffa45dcf, 564ac339c0f8bada4e77a57a92bab9d3df635e07, 8eb077025279304268bd58657f0af3d388822b21, ba5c0f28a26e7d9be1e0997f8920dd638e2782fd, 6.12.105, 6.14, 6.15 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.