# CVE-2024-46764: bpf: add check for invalid name in btf_name_valid_section()

> An out-of-bounds read in the Linux kernel BPF subsystem allows attackers to disclose memory or cause a denial of service via crafted BTF names.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-46764, DEBIAN-CVE-2024-46764, GHSA-324v-cwrv-qmqr, UBUNTU-CVE-2024-46764

## What is CVE-2024-46764?

CVE-2024-46764 is a high-severity memory corruption vulnerability in Linux kernel, published on 18 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-46764?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-46764?

Apply the vendor's patch.

## Is CVE-2024-46764 being exploited?

There is no known exploitation of CVE-2024-46764 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-46764 and fix it if it is affected.

What it is: CVE-2024-46764 is a high-severity memory corruption vulnerability in Linux kernel, published on 18 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-46764 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-46764/ (Markdown: https://insights.sbomify.com/CVE-2024-46764/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-46764
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-46764
- OSV: https://osv.dev/vulnerability/CVE-2024-46764

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-46764/
Summaries are generated and may contain mistakes; the official description above is the record.