LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38574: libbpf: Prevent null-pointer dereference when prog to load has no BTF

In the Linux kernel, the following vulnerability has been resolved: libbpf: Prevent null-pointer dereference when prog to load has no BTF In bpf_objec_load_prog(), there's no guarantee that obj->btf is non-NULL when passing it to btf__fd(), and this function does not perform any check before dereferencing its argument (as bpf_object__btf_fd() used to do). As a consequence, we get segmentation fault errors in bpftool (for example) when trying to load programs that come without BTF information. v2: Keep btf__fd() in the fix instead of reverting to bpf_object__btf_fd().

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

Security readout for executives and security teams

Plain-English summary

This CVE is a reliability flaw in Linux libbpf. When a BPF program lacks BTF metadata, libbpf can dereference a null pointer and crash tools such as bpftool. The provided sources do not show data theft, privilege escalation, or active exploitation.

Executive priority

Treat this as a low-priority patch management item unless your business depends on automated eBPF loading workflows. It can disrupt observability, security tooling, or developer workflows, but the provided evidence does not support emergency action.

Technical view

In bpf_object_load_prog(), obj->btf is not guaranteed to exist before being passed to btf__fd(). Because btf__fd() dereferences its argument without a null check, loading BPF programs without BTF information can trigger a segmentation fault.

Likely exposure

Exposure is most likely on Linux systems or build and operations environments using affected kernel/libbpf code paths to load BPF programs without BTF metadata. The source bundle lists Linux 6.8, 6.8.12, 6.9.3, and 6.10 as affected context.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The described impact is a crash during BPF program loading, not a confirmed path to code execution or privilege escalation.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. Severity, CVSS, and CWE fields are absent. The root cause and crash condition are clear, but exploitability beyond local process denial of service is not established in the provided sources.

Mitigation direction

  • Check Linux vendor advisories for backported fixes to this libbpf issue.
  • Update affected Linux kernel or libbpf packages when vendor fixes are available.
  • For source builds, review inclusion of the referenced stable kernel commits.
  • Prioritize environments that routinely load custom eBPF programs.

Validation and detection

  • Inventory Linux systems and toolchains using affected kernel or libbpf versions.
  • Identify workflows that load BPF programs without BTF metadata.
  • Confirm vendor packages include fixes corresponding to the referenced commits.
  • Retest relevant bpftool or BPF-loading workflows after updating.
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-38574 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
2ADP 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxdf7c3f7d3a3ddab31ca8cfa9b86a8729ec43fd2e, df7c3f7d3a3ddab31ca8cfa9b86a8729ec43fd2e, df7c3f7d3a3ddab31ca8cfa9b86a8729ec43fd2eunaffected
LinuxLinux6.8, 0, 6.8.12, 6.9.3, 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.