CVE-2026-53322

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

vfio/pci: Clean up DMABUFs before disabling function

On device shutdown, make vfio_pci_core_close_device() call vfio_pci_dma_buf_cleanup() before the function is disabled via vfio_pci_core_disable(). This ensures that all access via DMABUFs is revoked before the function's BARs become inaccessible.

This fixes an issue where, if the function is disabled first, a tiny window exists in which the function's MSE is cleared and yet BARs could still be accessed via the DMABUF. The resources would also be freed and up for grabs by a different driver.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

June 26, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

vfio/pci: Clean up DMABUFs before disabling function - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d97708701434ce72968e771976aaf9d3438fcafd
generic

vfio/pci: Clean up DMABUFs before disabling function - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4f1000a30f67cf7d328059242776a858611d5ef9

Vendor Advisories for CVE-2026-53322(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-24ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-24ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-24ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-24ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-24ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-24ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-24ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-24ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (137 versions)7.0.10-1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 30× in last 7d / 154× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 242 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 21:47 UTCEG score recompute
  3. 2026-08-24 21:47 UTCVendor advisory
  4. 2026-08-24 21:47 UTCGHSA enrichment
  5. 2026-08-24 06:58 UTCVendor advisory
  6. 2026-08-24 06:58 UTCGHSA enrichment
  7. 2026-08-23 19:44 UTCVendor advisory
  8. 2026-08-23 19:44 UTCGHSA enrichment
  9. 2026-08-23 08:31 UTCEG score recompute
  10. 2026-08-23 08:31 UTCVendor advisory
  11. 2026-08-23 08:31 UTCGHSA enrichment
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 20:59 UTCVendor advisory
  14. 2026-08-22 20:59 UTCGHSA enrichment
  15. 2026-08-22 09:20 UTCEG score recompute
  16. 2026-08-22 09:20 UTCVendor advisory
  17. 2026-08-22 09:20 UTCGHSA enrichment
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-21 17:23 UTCVendor advisory
  20. 2026-08-21 17:23 UTCGHSA enrichment
  21. 2026-08-21 05:08 UTCVendor advisory
  22. 2026-08-21 05:08 UTCGHSA enrichment
  23. 2026-08-20 17:47 UTCVendor advisory
  24. 2026-08-20 17:47 UTCGHSA enrichment
  25. 2026-08-20 06:32 UTCEG score recompute
Show 75 more
  1. 2026-08-20 06:32 UTCVendor advisory
  2. 2026-08-20 06:32 UTCGHSA enrichment
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-19 10:56 UTCVendor advisory
  5. 2026-08-19 10:56 UTCGHSA enrichment
  6. 2026-08-18 23:30 UTCEG score recompute
  7. 2026-08-18 23:30 UTCVendor advisory
  8. 2026-08-18 23:30 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 07:13 UTCVendor advisory
  12. 2026-08-17 07:13 UTCGHSA enrichment
  13. 2026-08-16 20:00 UTCEG score recompute
  14. 2026-08-16 20:00 UTCVendor advisory
  15. 2026-08-16 20:00 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 08:01 UTCEG score recompute
  18. 2026-08-16 08:01 UTCVendor advisory
  19. 2026-08-16 08:01 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 20:48 UTCVendor advisory
  22. 2026-08-15 20:48 UTCGHSA enrichment
  23. 2026-08-15 09:32 UTCEG score recompute
  24. 2026-08-15 09:32 UTCVendor advisory
  25. 2026-08-15 09:32 UTCGHSA enrichment
  26. 2026-08-15 01:30 UTCEPSS rescore
  27. 2026-08-14 22:18 UTCVendor advisory
  28. 2026-08-14 22:18 UTCGHSA enrichment
  29. 2026-08-14 11:04 UTCVendor advisory
  30. 2026-08-14 11:04 UTCGHSA enrichment
  31. 2026-08-13 23:51 UTCEG score recompute
  32. 2026-08-13 23:51 UTCVendor advisory
  33. 2026-08-13 23:51 UTCGHSA enrichment
  34. 2026-08-13 22:00 UTCEPSS rescore
  35. 2026-08-13 12:37 UTCVendor advisory
  36. 2026-08-13 12:37 UTCGHSA enrichment
  37. 2026-08-13 01:19 UTCVendor advisory
  38. 2026-08-13 01:19 UTCGHSA enrichment
  39. 2026-08-12 14:06 UTCEG score recompute
  40. 2026-08-12 14:06 UTCVendor advisory
  41. 2026-08-12 14:06 UTCGHSA enrichment
  42. 2026-08-12 13:51 UTCEPSS rescore
  43. 2026-08-12 02:52 UTCVendor advisory
  44. 2026-08-12 02:52 UTCGHSA enrichment
  45. 2026-08-11 15:38 UTCEG score recompute
  46. 2026-08-11 15:38 UTCVendor advisory
  47. 2026-08-11 15:37 UTCGHSA enrichment
  48. 2026-08-11 04:24 UTCEG score recompute
  49. 2026-08-11 04:24 UTCVendor advisory
  50. 2026-08-11 04:24 UTCGHSA enrichment
  51. 2026-08-11 00:00 UTCEPSS rescore
  52. 2026-08-10 17:11 UTCVendor advisory
  53. 2026-08-10 17:11 UTCGHSA enrichment
  54. 2026-08-10 05:46 UTCVendor advisory
  55. 2026-08-10 05:46 UTCGHSA enrichment
  56. 2026-08-09 18:32 UTCEG score recompute
  57. 2026-08-09 18:32 UTCVendor advisory
  58. 2026-08-09 18:32 UTCGHSA enrichment
  59. 2026-08-09 13:46 UTCEPSS rescore
  60. 2026-08-09 07:19 UTCVendor advisory
  61. 2026-08-09 07:19 UTCGHSA enrichment
  62. 2026-08-08 20:06 UTCEG score recompute
  63. 2026-08-08 20:06 UTCVendor advisory
  64. 2026-08-08 20:06 UTCGHSA enrichment
  65. 2026-08-08 16:37 UTCEPSS rescore
  66. 2026-08-08 08:53 UTCVendor advisory
  67. 2026-08-08 08:53 UTCGHSA enrichment
  68. 2026-08-07 21:40 UTCEG score recompute
  69. 2026-08-07 21:40 UTCVendor advisory
  70. 2026-08-07 21:40 UTCGHSA enrichment
  71. 2026-08-07 10:26 UTCVendor advisory
  72. 2026-08-07 10:26 UTCGHSA enrichment
  73. 2026-08-06 23:13 UTCEG score recompute
  74. 2026-08-06 23:13 UTCVendor advisory
  75. 2026-08-06 23:12 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53322?
CVE-2026-53322 is a high vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Clean up DMABUFs before disabling function On device shutdown, make vfiopcicoreclosedevice() call vfiopcidmabufcleanup() before the function is disabled via vfiopcicore_disable(). This ensures that all access via DMABUFs…
When was CVE-2026-53322 disclosed?
CVE-2026-53322 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53322 actively exploited?
CVE-2026-53322 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.2% of all scored CVEs.
What is the CVSS score of CVE-2026-53322?
CVE-2026-53322 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53322?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53322, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53322

Explore →

Is Your Infrastructure Affected by CVE-2026-53322?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs