FKIE_CVE-2026-80894
Vulnerability from fkie_nvd - Published: 2026-09-04 18:17 - Updated: 2026-09-04 18:17
Severity
Summary
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.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/iommu/iommufd/device.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "adb87155b67f9759ff010c0a99559f5bffa45dcf",
"status": "affected",
"version": "6d11543bf37abdf60b8e6022a62fccfb82a5fe2e",
"versionType": "git"
},
{
"lessThan": "564ac339c0f8bada4e77a57a92bab9d3df635e07",
"status": "affected",
"version": "fb21b1568adaa76af7a8c853f37c60fba8b28661",
"versionType": "git"
},
{
"lessThan": "8eb077025279304268bd58657f0af3d388822b21",
"status": "affected",
"version": "fb21b1568adaa76af7a8c853f37c60fba8b28661",
"versionType": "git"
},
{
"lessThan": "ba5c0f28a26e7d9be1e0997f8920dd638e2782fd",
"status": "affected",
"version": "fb21b1568adaa76af7a8c853f37c60fba8b28661",
"versionType": "git"
},
{
"status": "affected",
"version": "1e0216b6a58c79b5ee91c78706d5f560e4d1f56f",
"versionType": "git"
},
{
"status": "affected",
"version": "4b23c4b991eb90cc7bca42e9f81142feedd4bb56",
"versionType": "git"
},
{
"lessThan": "6.12.105",
"status": "affected",
"version": "6.12.24",
"versionType": "semver"
},
{
"lessThan": "6.14",
"status": "affected",
"version": "6.13.12",
"versionType": "semver"
},
{
"lessThan": "6.15",
"status": "affected",
"version": "6.14.3",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/iommu/iommufd/device.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.15"
},
{
"lessThan": "6.15",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.105",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.44",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.8",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommufd: Fix wrong hwpt passed to iommufd_auto_response_faults on replace\n\niommufd_hwpt_replace_device() calls:\n\n\tiommufd_auto_response_faults(hwpt, old_handle);\n\npassing the *new* hwpt together with the handle of\nthe device\u0027s *old* domain. This should be a parameter mismatch:\n\n1. Semantically, iommufd_auto_response_faults(x, handle) scans\n x-\u003efault\u0027s deliver list and response xarray for groups matching\n \"handle\". A group is queued under the hwpt that was attached at\n fault-delivery time. old_handle is fetched *before* the domain switch,\n so its group lives on old-\u003efault, not on the new hwpt-\u003efault.\n\n2. Historically, the first argument was \"old\". The routine was\n introduced by commit b7d8833677ba (\"iommufd: Fault-capable hwpt\n attach/detach/replace\") as __fault_domain_replace_dev() in\n fault.c, correctly calling iommufd_auto_response_faults(old, curr).\n Commit fb21b1568ada (\"iommufd: Make attach_handle generic than\n fault specific\") moved this into iommufd_hwpt_replace_device() in\n device.c and swapped it to \"hwpt\". This should be a refactor regression,\n not an intentional change.\n\nFix this by passing \"old\" instead."
}
],
"id": "CVE-2026-80894",
"lastModified": "2026-09-04T18:17:57.603",
"metrics": {},
"published": "2026-09-04T18:17:57.603",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/564ac339c0f8bada4e77a57a92bab9d3df635e07"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8eb077025279304268bd58657f0af3d388822b21"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/adb87155b67f9759ff010c0a99559f5bffa45dcf"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ba5c0f28a26e7d9be1e0997f8920dd638e2782fd"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Loading…
Loading…