Kernel stack corruption via unchecked upper-device enumeration
Published Mar 25, 2026 · Updated Mar 25, 2026
Out-of-bounds write in affected Linux Kernel versions allows local users to corrupt kernel stack memory through an XDP devmap redirect. In kernel/bpf/devmap.c, get_upper_ifindexes() writes every upper-device index into a fixed stack array without enforcing its MAX_NEST_DEV capacity. The trigger requires more than eight upper devices, such as macvlans, plus an attached XDP program using BPF_F_BROADCAST and BPF_F_EXCLUDE_INGRESS; the public record establishes memory corruption but no reliable privilege-escalation outcome.
Summary
What happened
Out-of-bounds write in affected Linux Kernel versions allows local users to corrupt kernel stack memory through an XDP devmap redirect. In kernel/bpf/devmap.c, get_upper_ifindexes() writes every upper-device index into a fixed stack array without enforcing its MAX_NEST_DEV capacity. The trigger requires more than eight upper devices, such as macvlans, plus an attached XDP program using BPF_F_BROADCAST and BPF_F_EXCLUDE_INGRESS; the public record establishes memory corruption but no reliable privilege-escalation outcome.
The record
- CVE
- CVE-2026-23359
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.15
- Affected versionversion=aeea1b86f9363f3feabb496534d886f082a89f21 <5000e40acc8d0c36ab709662e32120986ac22e7e
- Affected versionversion=aeea1b86f9363f3feabb496534d886f082a89f21 <75d474702b2ba8b6bcb26eb3004dbc5e95ffd5d2
- Affected versionversion=aeea1b86f9363f3feabb496534d886f082a89f21 <8a95fb9df1105b1618872c2846a6c01e3ba20b45
- Affected versionversion=aeea1b86f9363f3feabb496534d886f082a89f21 <b7bf516c3ecd9a2aae2dc2635178ab87b734fef1
- Affected versionversion=aeea1b86f9363f3feabb496534d886f082a89f21 <ca831567908fd3f73cf97d8a6c09a5054697a182
- Affected versionversion=aeea1b86f9363f3feabb496534d886f082a89f21 <d2c31d8e03d05edc16656e5ffe187f0d1da763d7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo