GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel BPF: bpf_get_stackid runs get_perf_callchain preemptible, exposing its trace buffer

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

Impact

bpf_get_stackid() called get_perf_callchain() and then read the returned per-CPU trace-entry buffer without disabling preemption, so the task can be scheduled off and the buffer reused underneath it. The upstream record is a one-paragraph fix with no exploitation analysis; NVD scores it as local high-impact, but the reachable consequence is a corrupted or attacker-influenced stack-trace buffer rather than a demonstrated escalation path. It matters on GPU nodes only insofar as fleet-wide observability agents (profilers, continuous-profiling daemons, eBPF security agents) run stack-map programs on every host, so the affected code path is loaded on essentially all of them.

Who can reach it

Local, and privileged: loading a BPF program that calls bpf_get_stackid requires CAP_BPF plus CAP_PERFMON (or root). Unprivileged tenants cannot reach it unless the node permits unprivileged BPF.

What to do

Pick up the stable-kernel update that adds the preempt_disable() around the callchain use. Kernel patch means drain and reboot the node; there is no module reload or daemon restart that fixes it. No mitigation is needed on nodes where only trusted observability agents hold CAP_BPF.

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.