Linux KernelOperating system · Linux
CVE-2026-52953
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Linux kernel's IOMMU VT-d driver has a NULL pointer dereference or out-of-bounds access vulnerability in domain_remove_dev_pasid(). The global static 'blocked domain' is a dummy domain without a corresponding dmar_domain structure, but the code attempts to access memory beyond the iommu_domain structure, triggering a general protection fault during device reset operations such as QEMU process termination.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
>= 6.6, < 6.18.33>= 6.19, < 7.0.10= 7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the running kernel versionRun 'uname -r' or 'cat /proc/version' to get the kernel version, then compare it to the affected ranges: < 6.18.33, >= 6.19 and < 7.0.10, or 7.1Affected if The kernel version falls within >= 6.6, < 6.18.33; >= 6.19, < 7.0.10; or = 7.1
-
Verify IOMMU VT-d driver is loadedCheck for Intel VT-d DMAR tables and driver: 'dmesg | grep -i dmar' and 'lsmod | grep intel_iommu' or check /sys/bus/pci/drivers/ for intel_iommuAffected if The Intel IOMMU VT-d driver (intel_iommu) is loaded and active
-
Confirm PASID-enabled devices existCheck for devices with PASID support by examining 'cat /sys/bus/pci/devices/*/pasid_enabled' or using 'lspci' to identify Intel Scalable I/O Virtualization capable devicesAffected if PCI devices with PASID (Process Address Space ID) support are present and assigned to VMs or using IOMMU passthrough
-
Check for VM or container usage with PCI passthroughReview active libvirt/qemu configurations: 'virsh list --all' and check for devices assigned to VMs, or check if container runtimes are using IOMMU-backed device assignmentAffected if QEMU/KVM virtual machines or containers are using PCI device passthrough with IOMMU, as the bug triggers during device reset operations like QEMU process termination
A system is affected if it runs a vulnerable kernel version (6.6 through 6.18.32, 6.19 through 7.0.9, or 7.1), has Intel VT-d IOMMU enabled, uses PASID-capable devices, and performs device reset operations such as QEMU process termination with assigned devices.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.18.337.0.10
This kernel bug requires patching the Linux kernel source code to add an early return check for blocked domains in domain_remove_dev_pasid(), similar to how identity domains are handled. Distributors should pull the relevant kernel update.
Linux Kernel 6.18.33 / 7.0.10 / 7.2 (or later stable release)
- Identify the currently running Linux kernel version using `uname -r`
- Check if the running kernel version falls within the affected range: >= 6.6 and < 6.18.33, or >= 6.19 and < 7.0.10, or 7.1
- If affected, schedule a maintenance window for kernel upgrade
- Upgrade the Linux kernel to version 6.18.33 or later, OR version 7.0.10 or later, OR version 7.2 or later
- Reboot the system to load the new kernel
- Verify the new kernel version is running using `uname -r`
- Confirm the vulnerability is resolved by checking that the patch is present in the kernel source (look for the early return in domain_remove_dev_pasid function)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,712.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-52953 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-52953 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data