CVE-2024-42072: bpf: Fix may_goto with negative offset.
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix may_goto with negative offset.
Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto.
The 1st bug is the way may_goto is patched. When offset is negative
it should be patched differently.
The 2nd bug is in the verifier:
when current state may_goto_depth is equal to visited state may_goto_depth
it means there is an actual infinite loop. It's not correct to prune
exploration of the program at this point.
Note, that this check doesn't limit the program to only one may_goto insn,
since 2nd and any further may_goto will increment may_goto_depth only
in the queued state pushed for future exploration. The current state
will have may_goto_depth == 0 regardless of number of may_goto insns
and the verifier has to explore the program until bpf_exit.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux kernel’s BPF handling can let a locally authenticated, low-privilege user trigger incorrect control-flow processing. The supplied CVSS assessment indicates possible compromise of confidentiality, integrity, and availability. This is primarily a host privilege-boundary risk, not a remotely exploitable network flaw.
Executive priority
Treat as a high-priority local privilege-boundary issue. Accelerate patching on shared, multi-user, container-hosting, and other systems exposed to untrusted local workloads. Internet-facing status alone does not determine exposure because the stated attack vector is local.
Technical view
The defect affects BPF may_goto processing. Negative offsets were patched incorrectly, and the verifier could prune exploration when equal may_goto_depth values actually represented an infinite loop. A crafted BPF program discovered by syzbot exposed both conditions. The supplied CVSS v3.1 score is 7.8 with local, low-privilege access required and no user interaction.
Likely exposure
The bundle identifies Linux kernel 6.9-related versions as affected and provides two stable-kernel fix commits. Exact version boundaries and downstream distribution package mappings are unclear in the supplied evidence. Exposure is most relevant where low-privilege local users or workloads can reach BPF functionality.
Exploitation context
The CVE is not listed as KEV in the supplied bundle. A syzbot-crafted BPF program exposed the bugs, but the sources provide no evidence of active exploitation or a public weaponized exploit.
Researcher notes
The two documented defects concern negative-offset instruction patching and verifier state pruning around may_goto_depth. The source bundle does not provide a CWE, precise downstream package matrix, demonstrated privilege escalation chain, or exploitation telemetry. Validate remediation by fix inclusion rather than relying solely on ambiguous version labels.
Mitigation direction
Apply vendor-supported kernel updates that incorporate the referenced stable-kernel fixes.
Check Linux distribution advisories for the exact fixed package version.
Prioritize multi-user and shared-workload systems where low-privilege local access exists.
Restrict unnecessary local access while affected systems await vendor updates.
Validation and detection
Inventory running kernel versions across Linux hosts.
Confirm installed kernel packages contain either referenced stable-kernel fix.
Verify systems rebooted into the updated kernel after installation.
Review whether low-privilege users or workloads can access BPF functionality.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-42072 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.