# CVE-2024-46754: bpf: Remove tst_run from lwt_seg6local_prog_ops.

> A null pointer dereference in the Linux kernel BPF subsystem allows local attackers to cause a denial of service via the lwt_seg6local test run function.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 2 Sep 2026
- **Also known as:** AZL-62615, AZL-68297, BELL-CVE-2024-46754, DEBIAN-CVE-2024-46754, GHSA-crwm-whhx-38v8, ROOT-OS-DEBIAN-11-CVE-2024-46754, ROOT-OS-DEBIAN-12-CVE-2024-46754, ROOT-OS-UBUNTU-2204-CVE-2024-46754, UBUNTU-CVE-2024-46754

## What is CVE-2024-46754?

CVE-2024-46754 is a high-severity 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: Remove tst_run from lwt_seg6local_prog_ops.

The syzbot reported that the lwt_seg6 related BPF ops can be invoked
via bpf_test_run() without without entering input_action_end_bpf()
first.

Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL
probably didn't work since it was introduced in commit 04d4b274e2a
("ipv6: sr: Add seg6local action End.BPF"). The reason is that the
per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self
test case but each BPF function expects it.

Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-46754 being exploited?

There is no known exploitation of CVE-2024-46754 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-46754 and fix it if it is affected.

What it is: CVE-2024-46754 is a high-severity 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-46754 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-46754/ (Markdown: https://insights.sbomify.com/CVE-2024-46754/index.md)
```

## Sources

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

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