cveboard RSS feed

CVE-2026-80894

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

iommufd: Fix wrong hwpt passed to iommufd_auto_response_faults on replace

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
6d11543bf37abdf60b8e6022a62fccfb82a5fe2eaffectedgitadb87155b67f9759ff010c0a99559f5bffa45dcfUnavailableNone listed
fb21b1568adaa76af7a8c853f37c60fba8b28661affectedgit564ac339c0f8bada4e77a57a92bab9d3df635e07UnavailableNone listed
fb21b1568adaa76af7a8c853f37c60fba8b28661affectedgit8eb077025279304268bd58657f0af3d388822b21UnavailableNone listed
fb21b1568adaa76af7a8c853f37c60fba8b28661affectedgitba5c0f28a26e7d9be1e0997f8920dd638e2782fdUnavailableNone listed
1e0216b6a58c79b5ee91c78706d5f560e4d1f56faffectedgitUnavailableUnavailableNone listed
4b23c4b991eb90cc7bca42e9f81142feedd4bb56affectedgitUnavailableUnavailableNone listed
6.12.24affectedsemver6.12.105UnavailableNone listed
6.13.12affectedsemver6.14UnavailableNone listed
6.14.3affectedsemver6.15UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
6.15affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver6.15UnavailableNone listed
6.12.105unaffectedsemverUnavailable6.12.*None listed
6.18.44unaffectedsemverUnavailable6.18.*None listed
7.1.8unaffectedsemverUnavailable7.1.*None listed
7.2unaffectedoriginal_commit_for_fixUnavailable*None listed