GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel BPF: LPM trie RCU annotations reject sleepable programs and spam lockdep warnings

CVSS 7.8CVE-2026-64352Kernel, userspace & hypervisorcurated

Impact

The commit is explicit that there is no use-after-free here: Tasks Trace RCU already serializes against the trie's reclaim path, and the observable effect is a 'suspicious RCU usage' splat once per callsite on lockdep-enabled kernels. What is affected is any node running a sleepable BPF LSM program that touches an LPM trie, which on GPU clusters usually means Cilium or Tetragon-style policy tooling. NVD carries CVSS 7.8 with high confidentiality and integrity impact; nothing in the record supports that reading, and kernels built without RCU lockdep checking see no behaviour change at all. This is a correctness and annotation fix, not a reason to open a maintenance window tonight.

Who can reach it

Local, and only on lockdep-enabled kernels: any process that triggers a sleepable BPF LSM hook which does an LPM trie lookup, update or delete. Production kernels without CONFIG_PROVE_RCU show no observable effect, and no privilege boundary is crossed.

What to do

Pick the fix up with your next scheduled kernel update; five stable commits are linked. It changes rcu_dereference_check() and rcu_dereference_protected() annotations only, so no out-of-band maintenance is warranted on production kernels. If you run lockdep kernels in a test fleet and the splats are drowning the logs, apply the same commits there.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.