CVE-2026-98075

bpf: reject BPF_PSEUDO_FUNC reference to the main program

N/A
Published: September 25, 2026 at 10:24 AM UTC
Updated: October 19, 2026 at 10:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: reject BPF_PSEUDO_FUNC reference to the main program fixups.c:jit_subprogs() rewrites BPF_PSEUDO_FUNC loads to contain real function addresses. This function is invoked from bpf_jit_subprogs() only when env->subprog_cnt > 1. Meaning that for any program like below: int main(void *ctx) { void *ptr = main; ... bpf_timer_set_callback(..., ptr); ... } The 'ptr' won't be ever converted to contain an address. In combination with e.g. bpf_timer_set_callback() this would lead to a function call at a bogus address. Instead of complicating the implementation, just assume that no useful program needs main to be a sync or async callback and reject BPF_PSEUDO_FUNC loads for the main subprogram.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.1369c087ba6225b574afb6e505b72cb75242a3d844
Vendor states this is fixed in 118212417ba0120d99f84154799f8880f07411f4 (fixed)
Vendor states this is fixed in 314c8caa9cb64ad60c5b969fe9a3e2dcdccf156f (fixed)
Vendor states this is fixed in 374b2c5561db80fcdd7cdce44af37a49416f61c7 (fixed)
Vendor states this is fixed in 8cb75f7ada25b1cf25f2f74dec3ba649b9064a09 (fixed)
Vendor states this is fixed in 92f0bd0e2b632c6565ac2214a4d7d2ed37e5b9f6 (fixed)
Vendor states this is fixed in c74750dca96f40a1adb9d334f5a3152f44b270c3 (fixed)
Vendor states this is fixed in d6c39774ae093c9f7009cc4ae918f18fc1af7ae7 (fixed)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusUNDERGOING ANALYSIS

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card