CVE-2024-46764: bpf: add check for invalid name in btf_name_valid_section()
In the Linux kernel, the following vulnerability has been resolved:
bpf: add check for invalid name in btf_name_valid_section()
If the length of the name string is 1 and the value of name[0] is NULL
byte, an OOB vulnerability occurs in btf_name_valid_section() and the
return value is true, so the invalid name passes the check.
To solve this, you need to check if the first position is NULL byte and
if the first character is printable.
Security readout for executives and security teams
Plain-English summary
A Linux kernel BPF type-information name check can accept a one-byte name containing only a null character and then access memory outside the intended bounds. A local, low-privileged attacker may be able to affect confidentiality, integrity, or availability. The supplied CVSS score is 7.3.
Executive priority
Prioritize remediation as high for systems accessible to untrusted local users. Internet reachability alone does not establish exposure because the supplied vector is local. Patch through normal emergency kernel processes after confirming vendor applicability, with particular attention to shared compute and other multi-user environments.
Technical view
btf_name_valid_section() fails to reject a length-one string whose first byte is null. The invalid name passes validation and triggers an out-of-bounds condition. The correction checks that the first byte is non-null and printable. The source bundle does not characterize the out-of-bounds access further.
Likely exposure
Exposure is limited to Linux systems running affected kernels where a low-privileged local actor can reach the vulnerable BPF/BTF processing path. The supplied affected-version data names 6.9, 6.10.10, and 6.11, but also contains an ambiguous “0” entry; confirm applicability through the system vendor.
Exploitation context
The CVSS vector describes local access, low privileges, low complexity, and no user interaction. CISA KEV status is false in the supplied bundle, and no cited source reports active exploitation or a public exploit. Treat exploitation status as unconfirmed, not absent.
Researcher notes
The defect is an input-validation boundary case in BTF section-name handling: length equals one and name[0] equals null. It both permits an invalid name and causes an out-of-bounds condition. The bundle provides two stable-kernel fix commits but does not establish exploitability details, affected distribution packages, or active exploitation.
Mitigation direction
Install a vendor-supported kernel update incorporating the referenced stable fixes.
Prioritize multi-user systems and hosts where untrusted local users receive accounts.
Check distribution or appliance vendor guidance for exact fixed package versions.
Restrict local access where patching cannot be completed promptly.
Validation and detection
Record each system’s running kernel version and vendor package release.
Compare installed packages with the vendor’s CVE-2024-46764 advisory or changelog.
Confirm the kernel source includes one of the referenced stable fixes or an equivalent backport.
Reboot updated systems and verify the newly installed kernel is running.
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-46764 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.
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.