CVE-2024-26589: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1b500d5d6cecf98dd6ca88bc9e7ae1783c83e6d3, 22c7fa171a02d310e3a3f6ed46a698ca8a0060ed, 29ffa63f21bcdcef3e36b03cccf9d0cd031f6ab0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1b500d5d6cecf98dd6ca88bc9e7ae1783c83e6d3, 22c7fa171a02d310e3a3f6ed46a698ca8a0060ed, 29ffa63f21bcdcef3e36b03cccf9d0cd031f6ab0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for validation. However, variable offset ptr alu is not prohibited for this ptr kind. So the variable offset is not checked. The following prog is accepted: func#0 @0 0: R1=ctx() R10=fp0 0: (bf) r6 = r1 ; R1=ctx() R6_w=ctx() 1: (79) r7 = *(u64 *)(r6 +144) ; R6_w=ctx() R7_w=flow_keys() 2: (b7) r8 = 1024 ; R8_w=1024 3: (37) r8 /= 1 ; R8_w=scalar() 4: (57) r8 &= 1024 ; R8_w=scalar(smin=smin32=0, smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400)) 5: (0f) r7 += r8 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &= 1024 mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1 mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024 6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024, var_off=(0x0; 0x400)) 6: (79) r0 = *(u64 *)(r7 +0) ; R0_w=scalar() 7: (95) exit This prog loads flow_keys to r7, and adds the variable offset r8 to r7, and finally causes out-of-bounds access: BUG: unable to handle page fault for address: ffffc90014c80038 [...] Call Trace: <TASK> bpf_dispatcher_nop_func include/linux/bpf.h:1231 [inline] __bpf_prog_run include/linux/filter.h:651 [inline] bpf_prog_run include/linux/filter.h:658 [inline] bpf_prog_run_pin_on_cpu include/linux/filter.h:675 [inline] bpf_flow_dissect+0x15f/0x350 net/core/flow_dissector.c:991 bpf_prog_test_run_flow_dissector+0x39d/0x620 net/bpf/test_run.c:1359 bpf_prog_test_run kernel/bpf/syscall.c:4107 [inline] __sys_bpf+0xf8f/0x4560 kernel/bpf/syscall.c:5475 __do_sys_bpf kernel/bpf/syscall.c:5561 [inline] __se_sys_bpf kernel/bpf/syscall.c:5559 [inline] __x64_sys_bpf+0x73/0xb0 kernel/bpf/syscall.c:5559 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Fix this by rejecting ptr alu with variable offset on flow_keys. Applying the patch rejects the program with "R7 pointer arithmetic on flow_keys prohibited".
- Published
- Feb 22, 2024
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-119
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.20affected
- d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 and later · before 7856cb9f0d795ce518a44c5d135dd932cfbfc656affected · git
- d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 and later · before 29ffa63f21bcdcef3e36b03cccf9d0cd031f6ab0affected · git
- d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 and later · before 4108b86e324da42f7ed425bd71632fd844300dc8affected · git
- d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 and later · before e8d3872b617c21100c5ee4f64e513997a68c2e3daffected · git
- d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 and later · before 1b500d5d6cecf98dd6ca88bc9e7ae1783c83e6d3affected · git
- d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 and later · before 22c7fa171a02d310e3a3f6ed46a698ca8a0060edaffected · git
- before 4.20not affected · semver
- 5.10.273 and later · up to and including 5.10.*not affected · semver
- 5.15.148 and later · up to and including 5.15.*not affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.20 and later · before 5.15.148
- linux linux kernel5.16.0 and later · before 6.1.75
- linux linux kernel6.2.0 and later · before 6.6.14
- linux linux kernel6.7.0 and later · before 6.7.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.76-1 | 6.1.76-1 |
| Debian:13 | linux | before 6.6.15-1 | 6.6.15-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52447Feb 22, 2024 · bpf: Defer the free of inner map when necessary26Monitor
- ← EarlierCVE-2023-52452Feb 22, 2024 · bpf: Fix accesses to uninit stack slots31Monitor
- Later →CVE-2024-26593Feb 23, 2024 · i2c: i801: Fix block process call transactions28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1b500d5d6cecf98dd6ca88bc9e7ae1783c83e6d3 | Vendor (CNA) |
| Linux Linux | 22c7fa171a02d310e3a3f6ed46a698ca8a0060ed | Vendor (CNA) |
| Linux Linux | 29ffa63f21bcdcef3e36b03cccf9d0cd031f6ab0 | Vendor (CNA) |
| Linux Linux | 4108b86e324da42f7ed425bd71632fd844300dc8 | Vendor (CNA) |
| Linux Linux | 7856cb9f0d795ce518a44c5d135dd932cfbfc656 | Vendor (CNA) |
| Linux Linux | e8d3872b617c21100c5ee4f64e513997a68c2e3d | Vendor (CNA) |
| debian:linux | 6.1.76-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-524401 days apartksmbd: fix slub overflow in ksmbd_decode_ntlmssp_auth_blob()38Monitor
- CVE-2021-4734889 days apartdrm/amd/display: Avoid HDCP over-read and corruption36Monitor
- CVE-2022-3640489 days apartLinux Kernel Bluetooth l2cap_core.c l2cap_conn_del use after free35Monitor
- CVE-2023-524342 days apartsmb: client: fix potential OOBs in smb2_parse_contexts()32Monitor
- CVE-2023-524440 days apartf2fs: fix to avoid dirent corruption31Monitor
- CVE-2024-265880 days apartLoongArch: BPF: Prevent out-of-bounds memory access31Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0126 · Feb 23, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/22c7fa171a02d310e3a3f6ed46a698ca8a0060ed
- git.kernel.org/stable/c/29ffa63f21bcdcef3e36b03cccf9d0cd031f6ab0
- git.kernel.org/stable/c/4108b86e324da42f7ed425bd71632fd844300dc8
- git.kernel.org/stable/c/7856cb9f0d795ce518a44c5d135dd932cfbfc656
- git.kernel.org/stable/c/e8d3872b617c21100c5ee4f64e513997a68c2e3d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.