iommufd: Fix wrong hwpt passed to iommufd_auto_response_faults on replace
Summary
| CVE | CVE-2026-80894 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-04 18:17:57 UTC |
| Updated | 2026-09-04 18:17:57 UTC |
| 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. |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.063210000 (date 2026-09-06)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 6d11543bf37abdf60b8e6022a62fccfb82a5fe2e adb87155b67f9759ff010c0a99559f5bffa45dcf git | Not specified |
| CNA | Linux | Linux | affected fb21b1568adaa76af7a8c853f37c60fba8b28661 564ac339c0f8bada4e77a57a92bab9d3df635e07 git | Not specified |
| CNA | Linux | Linux | affected fb21b1568adaa76af7a8c853f37c60fba8b28661 8eb077025279304268bd58657f0af3d388822b21 git | Not specified |
| CNA | Linux | Linux | affected fb21b1568adaa76af7a8c853f37c60fba8b28661 ba5c0f28a26e7d9be1e0997f8920dd638e2782fd git | Not specified |
| CNA | Linux | Linux | affected 1e0216b6a58c79b5ee91c78706d5f560e4d1f56f git | Not specified |
| CNA | Linux | Linux | affected 4b23c4b991eb90cc7bca42e9f81142feedd4bb56 git | Not specified |
| CNA | Linux | Linux | affected 6.12.24 6.12.105 semver | Not specified |
| CNA | Linux | Linux | affected 6.13.12 6.14 semver | Not specified |
| CNA | Linux | Linux | affected 6.14.3 6.15 semver | Not specified |
| CNA | Linux | Linux | affected 6.15 | Not specified |
| CNA | Linux | Linux | unaffected 6.15 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.105 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.44 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.8 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/ba5c0f28a26e7d9be1e0997f8920dd638e2782fd | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8eb077025279304268bd58657f0af3d388822b21 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/564ac339c0f8bada4e77a57a92bab9d3df635e07 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/adb87155b67f9759ff010c0a99559f5bffa45dcf | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.