CVE-2026-53281

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:

iommu/vt-d: Avoid NULL pointer dereference or refcount corruption

Commit 60f030f7418d ("iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE") fixed a NULL pointer dereference in an unlikely situation partly.

If dev_pasid is not found in the dev_pasids list, it remains NULL. However, the teardown operations are executed unconditionally, this lead to a NULL pointer dereference or refcount corruption.

If the domain was never attached to this IOMMU, info will be NULL, which would cause an immediate dereference when checking --info->refcnt.

Even if info is not NULL, decrementing the refcount without having removed a valid PASID might unbalance the count. This could lead to premature dropping of the refcount to 0, potentially causing a use-after-free for the remaining active devices sharing the domain.

Fix it by returning early if dev_pasid is NULL, before executing the teardown operations.

Issue found by AI review and suggested by Kevin Tian. https://sashiko.dev/#/patchset/20260421031347.1408890-1-zhenzhong.duan%40intel.com

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
3%
KEV
Not listed

Published

June 26, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

iommu/vt-d: Avoid NULL pointer dereference or refcount corruption - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/vt-d: Avoid NULL pointer dereference or refcount corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9022cb9ac0c2a72a57fa8ebf92ac74f953ca0153
generic

iommu/vt-d: Avoid NULL pointer dereference or refcount corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79ea2feb917b05366b49d85573c9c5331f043b2c

Vendor Advisories for CVE-2026-53281(2)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
redhatkernel-0:5.14.0-687.31.1.el9_82026-07-28redhat
redhatkernel-0:6.12.0-211.40.1.el10_22026-07-28redhat

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 15× in last 7d / 65× 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 289 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53281?
CVE-2026-53281 is a high vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Avoid NULL pointer dereference or refcount corruption Commit 60f030f7418d ("iommu/vt-d: Avoid use of NULL after WARNONONCE") fixed a NULL pointer dereference in an unlikely situation partly. If devpasid is not found in…
When was CVE-2026-53281 disclosed?
CVE-2026-53281 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-53281 actively exploited?
CVE-2026-53281 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53281?
CVE-2026-53281 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53281?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53281, 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-53281

Explore →

Is Your Infrastructure Affected by CVE-2026-53281?

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

Start Free Scan →Browse All CVEs