CVE-2026-68337

bpf: Reject redirect helpers without a bpf_net_context

N/A
Published: August 10, 2026 at 12:03 PM UTC
Updated: September 21, 2026 at 02:17 PM 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 redirect helpers without a bpf_net_context The bpf_redirect*() helpers and skb_do_redirect() obtain the per-task bpf_redirect_info via bpf_net_ctx_get_ri(), which dereferences the current->bpf_net_context unconditionally. That context is established on the paths that run tc BPF such as sch_handle_{ingress,egress}(), *except* for the case where {cls,act}_bpf was attached to a proper qdisc. A program running from there reaches the NULL deref in two ways: * It calls bpf_redirect() directly, which dereferences the context at the top of the helper: tc qdisc add dev eth0 root handle 1: red limit 1MB min 10KB max 20KB \ avpkt 1000 burst 100 qevent early_drop block 10 tc filter add block 10 pref 1 bpf obj redirect.o * It simply returns TC_ACT_REDIRECT without helper call: tcf_qevent_handle() then dispatches to skb_do_redirect(), which dereferences the context Rather than extending bpf_net_context management into the qdisc path, make the redirect helpers refuse to operate when no context exists, and have tcf_qevent_handle() drop a TC_ACT_REDIRECT verdict instead of calling skb_do_redirect(). Previous behaviour was a crash, so nothing regresses by not supporting it.

Affected

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

5.9 ≤ v < 6.12.1115.9 ≤ v < 6.18.535.9 ≤ v < 7.1.65.9 ≤ v < 7.23625750f05ecce21a0fce429c1ff85acfffb461b5.9
Vendor states this is fixed in 0f2118b757509332bb0e65f90e5233766f14bb88 (fixed)
Vendor states this is fixed in 3f4920d165b29052255527d8ae7619e7ec132ece (fixed)
Vendor states this is fixed in aafb093adffad91d4d071e8a7e0dcd9b1d91c94a (fixed)
Vendor states this is fixed in cabfacbd5af09d3ae898ca224c4a1459e9bba15d (fixed)
Vendor states this is fixed in 5.9 (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 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (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

StatusRECEIVED

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