Skip to content
major vulnerability· requires attention

Affects Linux kernel VFIO PCI DMABUF; widely deployed; could enable kernel RCE, impacting servers and workloads.

Systems

CVE-2026-53322

8.8
High
EPSS 0.13%Patch availableJun 28, 2026

Linux kernel VFIO/PCI DMABUF cleanup fixes shutdown access window.

common questions

Is CVE-2026-53322 being exploited?

Not confirmed. CVE-2026-53322 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-53322?

CVE-2026-53322 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-53322?

Yes. A fix has been recorded for CVE-2026-53322. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-53322 affect?

CVE-2026-53322 affects Linux kernel (vfio/pci). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-53322?

Update kernel to version with VFIO DMABUF fix

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (vfio/pci)
impact

Remote code execution via DMABUF access during shutdown window; BARs could be accessed by other drivers.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 5d74781ebc86c5fa9e9d6934024c505412de9b52 and < 4f1000a30f67cf7d328059242776a858611d5ef9
  • affected>= 5d74781ebc86c5fa9e9d6934024c505412de9b52 and < d97708701434ce72968e771976aaf9d3438fcafd
  • affected6.19
vendor says fixed in< 6.19, >= 7.0.10 and <= 7.0.*, >= 7.1 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free