CVE-2026-53372

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

iommu/vt-d: Block PASID attachment to nested domain with dirty tracking

Kernel lacks dirty tracking support on nested domain attached to PASID, fails the attachment early if nesting parent domain is dirty tracking configured, otherwise dirty pages would be lost.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 29, 2026

Advisory Details (3)

Auto-updated Jul 29, 2026
No patch confirmed yet.
generic

iommu/vt-d: Block PASID attachment to nested domain with dirty tracking - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/vt-d: Block PASID attachment to nested domain with dirty tracking - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9009c1af5458322469fa9a4371081a4449c5947d
generic

iommu/vt-d: Block PASID attachment to nested domain with dirty tracking - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3ea9ce757bd3de955b56e7bc5672fc479e40b045

Vendor Advisories for CVE-2026-53372(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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.7-1~bpo13+1 (133 versions)7.0.7-1—

All Vendor Advisories

(5)

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 23× in last 7d / 112× 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 137 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-53372?
CVE-2026-53372 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Block PASID attachment to nested domain with dirty tracking Kernel lacks dirty tracking support on nested domain attached to PASID, fails the attachment early if nesting parent domain is dirty tracking configured,…
When was CVE-2026-53372 disclosed?
CVE-2026-53372 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53372 actively exploited?
CVE-2026-53372 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 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53372?
CVE-2026-53372 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53372?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53372, 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-53372

Explore →

Is Your Infrastructure Affected by CVE-2026-53372?

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

Start Free Scan →Browse All CVEs