CVE-2024-53099: bpf: Check validity of link->type in bpf_link_show_fdinfo()
In the Linux kernel, the following vulnerability has been resolved:
bpf: Check validity of link->type in bpf_link_show_fdinfo()
If a newly-added link type doesn't invoke BPF_LINK_TYPE(), accessing
bpf_link_type_strs[link->type] may result in an out-of-bounds access.
To spot such missed invocations early in the future, checking the
validity of link->type in bpf_link_show_fdinfo() and emitting a warning
when such invocations are missed.
Security readout for executives and security teams
Plain-English summary
CVE-2024-53099 is a Linux kernel BPF bug where reporting information about a BPF link can index outside an internal type-name table. The sources do not provide CVSS scoring, impact detail, or evidence of active exploitation. Treat it as a kernel maintenance issue requiring affected-version checks and vendor kernel updates.
Executive priority
Handle through normal kernel patch governance unless vendor guidance raises severity. Prioritize internet-facing, multi-tenant, container-hosting, and security-sensitive Linux systems because kernel bugs can have broad operational impact even when exploitability is unclear.
Technical view
The flaw is in bpf_link_show_fdinfo(). If a newly added link type does not invoke BPF_LINK_TYPE(), bpf_link_type_strs[link->type] may be accessed out of bounds. The fix adds validity checking for link->type and warns when future link types miss the required registration path.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions or distro kernels that include the vulnerable BPF code. The bundle lists Linux kernel versions including 5.7, 5.10.233, 5.15.176, 6.1.123, 6.6.62, 6.11.9, and 6.12; verify exact vendor backport status.
Exploitation context
The source bundle does not cite KEV listing, active exploitation, public exploit availability, or a practical attack path. The described trigger involves BPF link fdinfo handling, but the provided sources do not establish remote exploitability or privilege impact.
Researcher notes
Evidence is incomplete for severity, CWE, CVSS, and exploitability. The core issue is an out-of-bounds table access caused by missing BPF link type registration. Focus validation on kernel commit presence, distro backports, and whether BPF-heavy workloads increase reachability.
Mitigation direction
Update affected Linux kernels using vendor or distribution security guidance.
Review the referenced stable kernel commits for applicable fixed branches.
Apply Debian LTS kernel updates where those advisories match deployed systems.
Track vendor advisories for backported fixes and package-specific version mapping.
Validation and detection
Inventory kernel versions across servers, containers, and appliances.
Compare deployed kernels with vendor CVE advisories and stable branch fixes.
Confirm the running kernel includes the bpf_link_show_fdinfo() type validation fix.
Document exceptions where vendor status remains unclear or unsupported.
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-53099 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.
0CVSS vectors
3Timeline events
1ADP providers
9Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Nov 25, 2024, 21:21 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.