CVE-2024-46754: bpf: Remove tst_run from lwt_seg6local_prog_ops.
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.
Security readout for executives and security teams
Plain-English summary
A local Linux user may be able to trigger unsafe kernel behavior through a BPF test interface for IPv6 Segment Routing. The supplied CVSS assessment rates potential confidentiality, integrity, and availability impact as high. The kernel fix removes the unsupported test pathway.
Executive priority
Treat as a high-priority local privilege boundary risk, especially on shared or multi-user Linux hosts. Patch through normal emergency kernel processes after compatibility testing. It is less urgent than a remotely exploitable flaw on an internet-facing service, but potential system-wide impact justifies prompt remediation.
Technical view
bpf_test_run() could invoke BPF_PROG_TYPE_LWT_SEG6LOCAL operations without first entering input_action_end_bpf(). Consequently, the per-CPU seg6_bpf_srh_states::srh value was not initialized although related BPF functions expected it. The stable-kernel remediation removes test_run from lwt_seg6local_prog_ops.
Likely exposure
Exposure is local, requires low privileges according to CVSS, and concerns Linux systems containing the affected LWT_SEG6LOCAL BPF test operation. The bundle names Linux 4.18, 6.10.10, and 6.11, but does not provide sufficiently clear downstream distribution package ranges. Confirm applicability with each Linux vendor.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not identified as a CISA KEV entry. The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. No public exploit evidence is included.
Researcher notes
The reported defect is an invalid test execution path rather than a working LWT_SEG6LOCAL self-test. The bundle provides no CWE, crash details, exploit proof, or precise distribution mapping. Researchers should use the two stable-kernel commits and vendor backport records to establish affected code ancestry without assuming upstream version labels match packaged kernels.
Mitigation direction
Apply a vendor-supported kernel update containing the referenced stable-kernel fix.
Check distribution advisories for exact package versions and backport status.
Prioritize multi-user systems where local users can access relevant BPF functionality.
Use vendor guidance for temporary restrictions if immediate kernel updating is unavailable.
Validation and detection
Record running kernel and installed package versions across Linux assets.
Check vendor changelogs for CVE-2024-46754 or either referenced fix commit.
Confirm updated kernels are active after reboot, not merely installed.
Review local BPF access controls while avoiding disruptive production testing.
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-46754 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.