CVE-2026-90242
Severity unknownNo known exploitationFix availableiommu/vt-d: Fix iopf_refcount leak on RID domain replacement
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 11% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix iopf_refcount leak on RID domain replacement intel_iommu_attach_device() enables IOPF for the new domain but never disables it for the old one. device_block_translation(), called at the start of the function, tears down translation but does not touch any IOPF state; blocking_domain_attach_dev() has to call iopf_for_domain_remove() explicitly before invoking it for exactly this reason. identity_domain_attach_dev() has the same problem. Its comment claims that no PRI handling is needed because the device has been put in the blocking state, but the blocking state and the IOPF reference count are independent of each other. As a result, replacing a domain that has an iopf_handler with another domain at RID level leaks a reference in info->iopf_refcount. The count never drops back to zero, so iopf_queue_remove_device() is never called and iommu_disable_pci_pri() triggers its WARN_ON(info->iopf_refcount) when the device is released. The PASID paths already handle this correctly by way of iopf_for_domain_replace(); convert the two RID paths to do the same. Using the replace helper rather than a bare remove keeps the enable before the disable, so the reference count does not transiently reach zero and evict the device from the IOPF queue.
Patching and mitigation
- Patch status
- Fix available (source: Microsoft MSRC)
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- msrc.microsoft.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 17fce9d2336d952b95474248303e5e7d9777f2e0 before 243bf1e45e40be4705aae17c5044bf83df5f4a92 | 243bf1e45e40be4705aae17c5044bf83df5f4a92 | CVE Program |
| Linux | Linux | from 17fce9d2336d952b95474248303e5e7d9777f2e0 before 143cd37ce76527ddd6f6dbac4a89bde31fb8b0dc | 143cd37ce76527ddd6f6dbac4a89bde31fb8b0dc | CVE Program |
| Linux | Linux | from 17fce9d2336d952b95474248303e5e7d9777f2e0 before 236dd58fabd2e951b940a6ad88b81147899ed311 | 236dd58fabd2e951b940a6ad88b81147899ed311 | CVE Program |
| Linux | Linux | 6.16 | Not documented | CVE Program |
| Microsoft | azl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0 | Not documented | 0:6.18.57-1.1.azl4 | Microsoft MSRC |
| Linux | Linux (unaffected) | from 6.18.57 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.2.6 up to and including 7.2.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.3 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.16 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Advisory
Microsoft advisory published
Advisory change
Microsoft advisory revised (2.0): Information published.
Advisory change
Microsoft advisory revised (3.0): Information published.
Patch
Fix documented by Microsoft MSRC
Vendor guidance and references
- Microsoft Security Update Guide (opens in a new tab)vendor-advisory
- https://git.kernel.org/stable/c/143cd37ce76527ddd6f6dbac4a89bde31fb8b0dc (opens in a new tab)
- https://git.kernel.org/stable/c/236dd58fabd2e951b940a6ad88b81147899ed311 (opens in a new tab)
- https://git.kernel.org/stable/c/243bf1e45e40be4705aae17c5044bf83df5f4a92 (opens in a new tab)