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
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.2%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
44
EG Risk 44/100

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%
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

Published

June 26, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
Patch available.
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(13)

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 rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 6× in last 7d / 38× 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 304 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-02 17:56 UTCEPSS rescore
  4. 2026-10-01 19:50 UTCEPSS rescore
  5. 2026-09-30 15:03 UTCEPSS rescore
  6. 2026-09-29 15:22 UTCEPSS rescore
  7. 2026-09-28 13:51 UTCEPSS rescore
  8. 2026-09-27 13:48 UTCEPSS rescore
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 00:27 UTCEPSS rescore
  11. 2026-09-23 17:53 UTCEPSS rescore
  12. 2026-09-23 07:46 UTCEG score recompute
  13. 2026-09-23 07:46 UTCVendor advisory
  14. 2026-09-23 07:46 UTCGHSA enrichment
  15. 2026-09-20 20:16 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-18 07:09 UTCEG score recompute
  18. 2026-09-18 07:09 UTCVendor advisory
  19. 2026-09-18 07:09 UTCGHSA enrichment
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-14 00:58 UTCEG score recompute
  23. 2026-09-14 00:58 UTCVendor advisory
  24. 2026-09-14 00:58 UTCGHSA enrichment
  25. 2026-09-13 16:47 UTCEPSS rescore
Show 75 more
  1. 2026-09-13 09:30 UTCVendor advisory
  2. 2026-09-13 09:30 UTCGHSA enrichment
  3. 2026-09-12 15:31 UTCEG score recompute
  4. 2026-09-12 15:31 UTCVendor advisory
  5. 2026-09-12 15:31 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-10 09:35 UTCEPSS rescore
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 14:57 UTCEG score recompute
  11. 2026-09-06 14:57 UTCVendor advisory
  12. 2026-09-06 14:57 UTCGHSA enrichment
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 19:16 UTCEG score recompute
  20. 2026-08-30 19:16 UTCVendor advisory
  21. 2026-08-30 19:16 UTCGHSA enrichment
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-28 21:41 UTCEPSS rescore
  24. 2026-08-27 22:55 UTCEG score recompute
  25. 2026-08-27 22:55 UTCVendor advisory
  26. 2026-08-27 22:55 UTCGHSA enrichment
  27. 2026-08-27 14:25 UTCEPSS rescore
  28. 2026-08-26 14:46 UTCEPSS rescore
  29. 2026-08-25 13:49 UTCEPSS rescore
  30. 2026-08-25 01:07 UTCEG score recompute
  31. 2026-08-25 01:07 UTCVendor advisory
  32. 2026-08-25 01:07 UTCGHSA enrichment
  33. 2026-08-24 12:48 UTCEG score recompute
  34. 2026-08-24 12:48 UTCVendor advisory
  35. 2026-08-24 12:48 UTCGHSA enrichment
  36. 2026-08-23 22:27 UTCVendor advisory
  37. 2026-08-23 22:27 UTCGHSA enrichment
  38. 2026-08-23 10:09 UTCEG score recompute
  39. 2026-08-23 10:09 UTCVendor advisory
  40. 2026-08-23 10:08 UTCGHSA enrichment
  41. 2026-08-23 00:19 UTCEPSS rescore
  42. 2026-08-22 21:49 UTCVendor advisory
  43. 2026-08-22 21:49 UTCGHSA enrichment
  44. 2026-08-22 09:22 UTCEG score recompute
  45. 2026-08-22 09:22 UTCVendor advisory
  46. 2026-08-22 09:22 UTCGHSA enrichment
  47. 2026-08-21 23:49 UTCEPSS rescore
  48. 2026-08-21 19:36 UTCVendor advisory
  49. 2026-08-21 19:36 UTCGHSA enrichment
  50. 2026-08-21 07:18 UTCEG score recompute
  51. 2026-08-21 07:18 UTCVendor advisory
  52. 2026-08-21 07:18 UTCGHSA enrichment
  53. 2026-08-20 22:55 UTCEPSS rescore
  54. 2026-08-20 18:58 UTCVendor advisory
  55. 2026-08-20 18:58 UTCGHSA enrichment
  56. 2026-08-20 06:40 UTCEG score recompute
  57. 2026-08-20 06:40 UTCVendor advisory
  58. 2026-08-20 06:40 UTCGHSA enrichment
  59. 2026-08-19 17:04 UTCEPSS rescore
  60. 2026-08-19 12:37 UTCVendor advisory
  61. 2026-08-19 12:36 UTCGHSA enrichment
  62. 2026-08-18 23:39 UTCEG score recompute
  63. 2026-08-18 23:39 UTCVendor advisory
  64. 2026-08-18 23:38 UTCGHSA enrichment
  65. 2026-08-18 13:48 UTCEPSS rescore
  66. 2026-08-17 13:47 UTCEPSS rescore
  67. 2026-08-17 10:09 UTCVendor advisory
  68. 2026-08-17 10:09 UTCGHSA enrichment
  69. 2026-08-16 21:51 UTCEG score recompute
  70. 2026-08-16 21:51 UTCVendor advisory
  71. 2026-08-16 21:51 UTCGHSA enrichment
  72. 2026-08-16 14:56 UTCEPSS rescore
  73. 2026-08-16 09:32 UTCEG score recompute
  74. 2026-08-16 09:32 UTCVendor advisory
  75. 2026-08-16 09:32 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 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.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53281?
CVE-2026-53281 has a CVSS base score of 8.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2026-53281?
A fix for CVE-2026-53281 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53281 are linked in the Vendor Advisories panel on this page.

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.