LiveActive security incident?Get immediate response
CVE Record

CVE-2024-45020: bpf: Fix a kernel verifier crash in stacksafe()

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a kernel verifier crash in stacksafe() Daniel Hodges reported a kernel verifier crash when playing with sched-ext. Further investigation shows that the crash is due to invalid memory access in stacksafe(). More specifically, it is the following code: if (exact != NOT_EXACT && old->stack[spi].slot_type[i % BPF_REG_SIZE] != cur->stack[spi].slot_type[i % BPF_REG_SIZE]) return false; The 'i' iterates old->allocated_stack. If cur->allocated_stack < old->allocated_stack the out-of-bound access will happen. To fix the issue add 'i >= cur->allocated_stack' check such that if the condition is true, stacksafe() should fail. Otherwise, cur->stack[spi].slot_type[i % BPF_REG_SIZE] memory access is legal.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-45020 is a Linux kernel BPF verifier bug that can cause a kernel verifier crash from invalid memory access. The public record says the issue is resolved, but gives no CVSS score or confirmed exploitation. Treat this as a kernel stability and availability concern until your Linux vendor maps the fix to supported packages.

Executive priority

Set priority after asset inventory. Without a CVSS score or exploitation evidence, this is not clearly an emergency, but kernel verifier crashes can affect availability and should be remediated through normal kernel patch cycles, faster on systems allowing BPF-heavy workloads.

Technical view

The bug is in the BPF verifier stacksafe() logic. It iterates old->allocated_stack and can read past cur->allocated_stack when the current stack is smaller. The fix adds a bounds check so stacksafe() fails before accessing cur->stack out of bounds. Sources identify stable kernel fix commits but do not provide exploit mechanics.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds listed in the CVE metadata, including 6.7, 6.6.48, 6.10.7, and 6.11. The version data is incomplete and partly ambiguous, so organizations should rely on distribution advisories and kernel commit presence for confirmation.

Exploitation context

The source says the crash was reported while working with sched-ext and identifies invalid memory access in the verifier. CISA KEV status is false in the bundle, and no cited source confirms active exploitation, public exploit availability, or remote attack exposure.

Researcher notes

Evidence supports an out-of-bounds read in BPF verifier stack state comparison, fixed by bounding cur->allocated_stack before slot_type access. Public sources do not establish privilege requirements, reachability, impact beyond verifier crash, or exploitability. Avoid assuming remote exposure without vendor analysis.

Mitigation direction

  • Update Linux kernels using your distribution’s advisory for CVE-2024-45020.
  • Confirm the deployed kernel includes the referenced stable fix commits.
  • Prioritize systems that permit BPF or sched-ext experimentation.
  • Track vendor backports because package versions may not match upstream kernel numbers.
  • Avoid unsupported kernels where vendor remediation status cannot be verified.

Validation and detection

  • Inventory running kernel versions across Linux fleets.
  • Map each kernel package to vendor CVE-2024-45020 guidance.
  • Check whether the referenced stable commits are present or backported.
  • Record systems using affected upstream versions for remediation tracking.
  • Monitor KEV and vendor advisories for exploitation status changes.
Prepared
Confidence
medium
Sources
5

Public sources used

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-45020 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

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

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

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxab470fefce2837e66b771c60858118d50bb5bb10, 2793a8b015f7f1caadb9bce9c63dc659f7522676, 2793a8b015f7f1caadb9bce9c63dc659f7522676, 6.6.15unaffected
LinuxLinux6.7, 0, 6.6.48, 6.10.7, 6.11affected
Weakness

CWE details

No CWE listed

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