LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
4

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-42072Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux011832b97b311bb9e3c27945bc0d1089a14209c9, 011832b97b311bb9e3c27945bc0d1089a14209c9unaffected
LinuxLinux6.9, 0, 6.9.8, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.