CVE-2026-90387

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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

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

swiotlb: Preserve allocation virtual address for dynamic pools

swiotlb_alloc_tlb() can allocate from the DMA atomic pool when a decrypted pool is needed from atomic context. With CONFIG_DMA_DIRECT_REMAP, the atomic pool is backed by remapped virtual addresses, which are not the same as the direct-map addresses returned by phys_to_virt().

swiotlb_init_io_tlb_pool() currently reconstructs the pool virtual address from the physical start address. For atomic-pool backed allocations this stores the wrong address in pool->vaddr. Later, swiotlb_free_tlb() passes that address to dma_free_from_pool(), which will fail to recognize the chunk

Pass the virtual address returned by the allocation path into swiotlb_init_io_tlb_pool(), and store that address in pool->vaddr. This keeps the pool free path using the same virtual address as the allocator.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (5)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

swiotlb: Preserve allocation virtual address for dynamic pools - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57d29044d0f29a76c6ec0c112c8c7371d5608dc7
generic

swiotlb: Preserve allocation virtual address for dynamic pools - kernel/git/stable/linux.git - Linux kernel stable tree

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

swiotlb: Preserve allocation virtual address for dynamic pools - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35e0103177826430b5df888b1506239d41e76ab5
generic

swiotlb: Preserve allocation virtual address for dynamic pools - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45507dcb0847e96add4455274b12df0eca6590b4
generic

swiotlb: Preserve allocation virtual address for dynamic pools - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68bf3ebd8e7020dae58e8aa14c7d482738bff9a8

Vendor Advisories for CVE-2026-90387(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 38× in last 7d / 98× 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.

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

Frequently asked(5)

What is CVE-2026-90387?
CVE-2026-90387 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: swiotlb: Preserve allocation virtual address for dynamic pools swiotlballoctlb() can allocate from the DMA atomic pool when a decrypted pool is needed from atomic context. With CONFIGDMADIRECT_REMAP, the atomic pool is backed by…
When was CVE-2026-90387 disclosed?
CVE-2026-90387 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90387 actively exploited?
CVE-2026-90387 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-90387?
CVE-2026-90387 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90387?
No fix for CVE-2026-90387 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90387 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-90387

Explore →

Is Your Infrastructure Affected by CVE-2026-90387?

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

Book a Demo →Browse All CVEs