Re: [PATCH bpf-next v2 0/2] bpf: Invalidate RCU pointers after final spin unlock
[email protected] Tue, 04 Aug 2026 09:40:20 +0000
| Newsgroups | org.kernel.vger.bpf |
|---|---|
| Message-ID | <178583642064.3066243.929090840390958892.git-patchwork-notify@kernel.org> |
Hello: This series was applied to bpf/bpf-next.git (master) by Kumar Kartikeya Dwivedi <[email protected]>: On Mon, 3 Aug 2026 04:26:07 -0700 you wrote: > In a sleepable BPF program, a spin lock can provide the only RCU protection > for a kptr. The final 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 > KASAN-confirmed task_struct use-after-free. > > Patch 1 invalidates RCU-protected pointers only when an unlock leaves the > final RCU-protected context. Patch 2 adds a negative sleepable test and > positive controls for non-sleepable and explicit-RCU contexts. > > [...] Here is the summary with links: - [bpf-next,v2,1/2] bpf: Invalidate RCU pointers after final spin unlock https://git.kernel.org/bpf/bpf-next/c/180c7000712d - [bpf-next,v2,2/2] selftests/bpf: Test RCU pointer invalidation after spin unlock https://git.kernel.org/bpf/bpf-next/c/bb2df6fd891d You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html