GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel BPF: use-after-free race in bpf_trampoline_link_cgroup_shim when attaching cgroup LSM programs

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

Impact

Attaching a cgroup-scoped BPF program can take a reference to a shim link whose refcount has already dropped to zero while its release is still pending. A racing process can then use freed kernel memory. The fix author reports a proof of concept that crashes almost every time. The CVSS vector rates it as full confidentiality, integrity and availability loss on the host kernel, so a crash takes down every job on the GPU node, and successful memory corruption would compromise every tenant on it.

Who can reach it

Local. A process on the host that can load and attach BPF programs (the cgroup LSM shim path) and can race attach and release. The record does not state which capabilities are needed. Normally only privileged agents such as CNI, observability or security daemons can attach BPF, so a container without BPF privileges should not reach this path.

What to do

Install a kernel that includes the stable fix (the commits referenced below), then drain and reboot each node. Until then, audit which pods and daemons hold BPF privileges (CAP_BPF / CAP_SYS_ADMIN, privileged containers) and keep them limited.

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.