CVE-2026-23390

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-25. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.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: 7.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:

tracing/dma: Cap dma_map_sg tracepoint arrays to prevent buffer overflow

The dma_map_sg tracepoint can trigger a perf buffer overflow when tracing large scatter-gather lists. With devices like virtio-gpu creating large DRM buffers, nents can exceed 1000 entries, resulting in:

phys_addrs: 1000 * 8 bytes = 8,000 bytes dma_addrs: 1000 * 8 bytes = 8,000 bytes lengths: 1000 * 4 bytes = 4,000 bytes Total: ~20,000 bytes

This exceeds PERF_MAX_TRACE_SIZE (8192 bytes), causing:

WARNING: CPU: 0 PID: 5497 at kernel/trace/trace_event_perf.c:405 perf buffer not large enough, wanted 24620, have 8192

Cap all three dynamic arrays at 128 entries using min() in the array size calculation. This ensures arrays are only as large as needed (up to the cap), avoiding unnecessary memory allocation for small operations while preventing overflow for large ones.

The tracepoint now records the full nents/ents counts and a truncated flag so users can see when data has been capped.

Changes in v2:

  • Use min(nents, DMA_TRACE_MAX_ENTRIES) for dynamic array sizing
instead of fixed DMA_TRACE_MAX_ENTRIES allocation (feedback from Steven Rostedt)
  • This allocates only what's needed up to the cap, avoiding waste
for small operations

Reviwed-by: Sean Anderson

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

Published

March 25, 2026

Last Modified

June 17, 2026

Advisory Details (3)

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

tracing/dma: Cap dma_map_sg tracepoint arrays to prevent buffer overflow - kernel/git/stable/linux.git - Linux kernel stable tree

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

tracing/dma: Cap dma_map_sg tracepoint arrays to prevent buffer overflow - kernel/git/stable/linux.git - Linux kernel stable tree

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

tracing/dma: Cap dma_map_sg tracepoint arrays to prevent buffer overflow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02d209bb018a40dee9eac89e91860253dee9605b

Vendor Advisories for CVE-2026-23390(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.12.74osv

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.38-1 ... 6.12.73-1~bpo12+1 (13 versions)6.12.74-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (99 versions)6.18.13-1

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-23390?
CVE-2026-23390 is a high vulnerability published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: tracing/dma: Cap dmamapsg tracepoint arrays to prevent buffer overflow The dmamapsg tracepoint can trigger a perf buffer overflow when tracing large scatter-gather lists. With devices like virtio-gpu creating large DRM buffers,…
When was CVE-2026-23390 disclosed?
CVE-2026-23390 was first published in the National Vulnerability Database on March 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23390 actively exploited?
CVE-2026-23390 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-23390?
CVE-2026-23390 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23390?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23390, 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-23390

Explore →

Is Your Infrastructure Affected by CVE-2026-23390?

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