LiveActive security incident?Get immediate response
CVE Record

CVE-2021-45941: libbpf 0.6.0 and 0.6.1 has a heap-based buffer overflow (8 bytes) in __bpf_object__open (called from bpf_ob...

libbpf 0.6.0 and 0.6.1 has a heap-based buffer overflow (8 bytes) in __bpf_object__open (called from bpf_object__open_mem and bpf-object-fuzzer.c).

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

Security readout for executives and security teams

Plain-English summary

CVE-2021-45941 is a memory corruption issue in libbpf versions 0.6.0 and 0.6.1. The public record describes an 8-byte heap-based buffer overflow when opening eBPF object data. Business urgency depends on whether these versions are present and whether they process untrusted eBPF object files.

Executive priority

Prioritize as an exposure discovery item unless libbpf 0.6.0 or 0.6.1 is confirmed in production with untrusted input paths. No active exploitation evidence or severity score is provided in the source bundle.

Technical view

The issue is reported in __bpf_object__open, reached from bpf_object__open_mem and identified through OSS-Fuzz. The source bundle does not provide CVSS, CWE, affected CPEs, fixed versions, or exploitability details. Treat it as a targeted exposure assessment for libbpf 0.6.0 and 0.6.1 consumers.

Likely exposure

Exposure is most likely in systems, agents, build tools, or observability/security products that bundle or link libbpf 0.6.0 or 0.6.1 and open eBPF object data. Evidence is incomplete for downstream products, package names, and fixed versions.

Exploitation context

The bundle does not show CISA KEV listing, active exploitation, public exploit details, or in-the-wild reports. The cited origin appears to be OSS-Fuzz, so validation should focus on version presence and reachable parsing paths rather than assumed exploitation.

Researcher notes

The strongest public facts are the affected libbpf versions, the heap overflow location, and OSS-Fuzz provenance. The record lacks CVSS, CWE, fixed-version, and downstream product data, so avoid broad claims beyond confirmed libbpf 0.6.0 and 0.6.1 usage.

Mitigation direction

  • Inventory systems and software that include libbpf 0.6.0 or 0.6.1.
  • Check upstream libbpf and OS vendor guidance for fixed package versions.
  • Upgrade only to vendor-supported fixed builds when identified.
  • Avoid processing untrusted eBPF object files where affected versions remain.
  • Monitor the CVE and OSS-Fuzz references for updated remediation details.

Validation and detection

  • Search SBOMs, package manifests, and vendor inventories for libbpf 0.6.0 or 0.6.1.
  • Identify applications that call libbpf to open eBPF object data.
  • Confirm whether any eBPF object inputs come from users, tenants, or external sources.
  • Review security, tracing, networking, and observability agents for bundled libbpf.
  • Record compensating controls if affected versions cannot be removed quickly.
Prepared
Confidence
medium
Sources
4

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-2021-45941 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
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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