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.
Published: 2026-09-04
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: Fault handling failure leading to potential denial of service
Action: Apply patch
AI Analysis

Impact

The Linux kernel’s IOMMU fault handling module contains a logic error: during a device replacement, the function iommufd_auto_response_faults is invoked with the wrong hardware fault pointer. Instead of passing the old fault domain, the code mistakenly passes the new domain, causing the system to reference stale fault information. This incorrect parameter usage prevents the kernel from correctly delivering or responding to IOMMU faults for the affected device, which can interrupt fault processing, lead to kernel stalls, or cause degraded system stability.

Affected Systems

All Linux kernel releases that include the iommufd module and have not applied the corrective commit (identified by the references in the data). Distribution kernels shipped before the patch commit are affected; kernels that already incorporate the fix are safe. The issue is tied to the iommufd_hwpt_replace_device function and its interaction with iommufd_auto_response_faults, so environment setups that perform hot‑plug replacement of IOMMU devices are most relevant.

Risk and Exploitability

The vulnerability has no listed EPSS score and is not present in the CISA KEV catalog, indicating that no widespread exploitation is known. Exploitation would require local or privileged kernel access to trigger an IOMMU device replacement, so a remote exploitation vector is unlikely. The failure to handle faults can result in system instability or potential denial of service, which represents a moderate risk for workloads heavily reliant on IOMMU fault resilience.

Generated by OpenCVE AI on September 4, 2026 at 21:06 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest kernel update that includes the corrected iommufd_auto_response_faults call.
  • If a patched kernel is not immediately available, disable hot‑plug replacement of IOMMU devices to prevent the erroneous code path from executing.
  • Monitor kernel logs for signs of missed IOMMU faults or unusual fault handling activity, and apply the patch as soon as possible.

Generated by OpenCVE AI on September 4, 2026 at 21:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4788-1 linux-6.12 security update
History

Fri, 04 Sep 2026 21:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-398

Fri, 04 Sep 2026 17:30:00 +0000

Type Values Removed Values Added
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.
Title iommufd: Fix wrong hwpt passed to iommufd_auto_response_faults on replace
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-04T17:11:10.093Z

Reserved: 2026-08-26T14:34:25.800Z

Link: CVE-2026-80894

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-04T18:17:57.603

Modified: 2026-09-04T18:17:57.603

Link: CVE-2026-80894

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T21:30:07Z

Weaknesses