All reports
Medium

kernel: bpf: Invalidate RCU pointers after final spin unlock

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-90317

Probability of exploitation in the next 30 days: 0.17%

FIRST EPSS · 2026-11-20

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Invalidate RCU pointers after final spin unlock In a sleepable BPF program, a spin lock can provide the only RCU protection for a kptr. The final bpf_spin_unlock() ends that protection, but the verifier leaves the pointer valid. Another CPU can then free the object before the pointer is used. A capability-limited runtime PoC triggered a task_struct use-after-free in __bpf_get_task_stack(). Record whether the program is in an RCU-protected context before releasing the lock. Invalidate RCU-protected pointers only when the unlock leaves the final such context. This preserves valid pointers in non-sleepable programs and inside an explicit RCU read-side section.

A flaw was found in the Linux kernel's Berkeley Packet Filter (BPF) subsystem. In sleepable BPF programs, a use-after-free vulnerability can occur due to improper handling of RCU (Read-Copy-Update) protected pointers after a spin unlock operation. A local attacker with limited capabilities could exploit this flaw to trigger a task_struct use-after-free, potentially leading to a denial of service or privilege escalation.