Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23359bpf: Fix stack-out-of-bounds write in devmap

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23359, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 96% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected aeea1b86f9363f3feabb496534d886f082a89f21 – < 88df604f0d16a692867582350ce3f2fcd22243f1
    • affected aeea1b86f9363f3feabb496534d886f082a89f21 – < 5000e40acc8d0c36ab709662e32120986ac22e7e
    • affected aeea1b86f9363f3feabb496534d886f082a89f21 – < 8a95fb9df1105b1618872c2846a6c01e3ba20b45
    • affected aeea1b86f9363f3feabb496534d886f082a89f21 – < d2c31d8e03d05edc16656e5ffe187f0d1da763d7
    • affected aeea1b86f9363f3feabb496534d886f082a89f21 – < 75d474702b2ba8b6bcb26eb3004dbc5e95ffd5d2
    • affected aeea1b86f9363f3feabb496534d886f082a89f21 – < ca831567908fd3f73cf97d8a6c09a5054697a182
    • affected aeea1b86f9363f3feabb496534d886f082a89f21 – < b7bf516c3ecd9a2aae2dc2635178ab87b734fef1
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.77 – ≤ 6.12.*
    • unaffected 6.18.17 – ≤ 6.18.*
    • unaffected 6.19.7 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23359 badge
[![CVE-2026-23359](https://cveledger.app/badge/CVE-2026-23359.svg)](https://cveledger.app/cve/CVE-2026-23359)

Record last updated .