CVE-2026-45945

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 3 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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

iommu/vt-d: Fix race condition during PASID entry replacement

The Intel VT-d PASID table entry is 512 bits (64 bytes). When replacing an active PASID entry (e.g., during domain replacement), the current implementation calculates a new entry on the stack and copies it to the table using a single structure assignment.

struct pasid_entry *pte, new_pte;

pte = intel_pasid_get_entry(dev, pasid); pasid_pte_config_first_level(iommu, &new_pte, ...); *pte = new_pte;

Because the hardware may fetch the 512-bit PASID entry in multiple 128-bit chunks, updating the entire entry while it is active (Present bit set) risks a "torn" read. In this scenario, the IOMMU hardware could observe an inconsistent state — partially new data and partially old data — leading to unpredictable behavior or spurious faults.

Fix this by removing the unsafe "replace" helpers and following the "clear-then-update" flow, which ensures the Present bit is cleared and the required invalidation handshake is completed before the new configuration is applied.

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

May 27, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated May 31, 2026
No patch confirmed yet.
generic

iommu/vt-d: Fix race condition during PASID entry replacement - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/vt-d: Fix race condition during PASID entry replacement - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66a7aff480a82b8642b3991fed5fdc9780022157

Vendor Advisories for CVE-2026-45945(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.39osv

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 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-45945?
CVE-2026-45945 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix race condition during PASID entry replacement The Intel VT-d PASID table entry is 512 bits (64 bytes). When replacing an active PASID entry (e.g., during domain replacement), the current implementation calculates a…
When was CVE-2026-45945 disclosed?
CVE-2026-45945 was first published in the National Vulnerability Database on May 27, 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-45945 actively exploited?
CVE-2026-45945 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 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-45945?
CVE-2026-45945 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-45945?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45945, 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-45945

Explore →

Is Your Infrastructure Affected by CVE-2026-45945?

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