CVE-2026-23359

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
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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:

bpf: Fix stack-out-of-bounds write in devmap

get_upper_ifindexes() iterates over all upper devices and writes their indices into an array without checking bounds.

Also the callers assume that the max number of upper devices is MAX_NEST_DEV and allocate excluded_devices[1+MAX_NEST_DEV] on the stack, but that assumption is not correct and the number of upper devices could be larger than MAX_NEST_DEV (e.g., many macvlans), causing a stack-out-of-bounds write.

Add a max parameter to get_upper_ifindexes() to avoid the issue. When there are too many upper devices, return -EOVERFLOW and abort the redirect.

To reproduce, create more than MAX_NEST_DEV(8) macvlans on a device with an XDP program attached using BPF_F_BROADCAST | BPF_F_EXCLUDE_INGRESS. Then send a packet to the device to trigger the XDP redirect path.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
3.1%
KEV
Not listed

Published

March 25, 2026

Last Modified

July 14, 2026

Advisory Details (7)

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

bpf: Fix stack-out-of-bounds write in devmap - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix stack-out-of-bounds write in devmap - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix stack-out-of-bounds write in devmap - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix stack-out-of-bounds write in devmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a95fb9df1105b1618872c2846a6c01e3ba20b45
generic

bpf: Fix stack-out-of-bounds write in devmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88df604f0d16a692867582350ce3f2fcd22243f1
generic

bpf: Fix stack-out-of-bounds write in devmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75d474702b2ba8b6bcb26eb3004dbc5e95ffd5d2
generic

bpf: Fix stack-out-of-bounds write in devmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5000e40acc8d0c36ab709662e32120986ac22e7e

Vendor Advisories for CVE-2026-23359(2)

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.1.167osv

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 48× 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 125 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23359?
CVE-2026-23359 is a high vulnerability published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix stack-out-of-bounds write in devmap getupperifindexes() iterates over all upper devices and writes their indices into an array without checking bounds. Also the callers assume that the max number of upper devices is…
When was CVE-2026-23359 disclosed?
CVE-2026-23359 was first published in the National Vulnerability Database on March 25, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23359 actively exploited?
CVE-2026-23359 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-23359?
CVE-2026-23359 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23359?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23359, 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

Explore the affected products and dependency analysis for CVE-2026-23359

Explore →

Is Your Infrastructure Affected by CVE-2026-23359?

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