GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel BPF: wrong bpf_xdp_store_bytes argument type lets the helper read uninitialized memory

CVSS 5.5CVE-2026-45886Kernel, userspace & hypervisorcurated

Impact

bpf_xdp_store_bytes declared its source buffer as ARG_PTR_TO_UNINIT_MEM, which both made the verifier demand write access to a read-only map value (breaking legitimate XDP programs that source bytes from a BPF_F_RDONLY_PROG map, as hit in Cilium) and allowed the helper to read from memory the program never initialized. The security-relevant half is the second: stale kernel stack or map bytes can be written into packets on the wire. Exposure is limited to whoever may load XDP programs, which on a GPU node is the CNI and the node's networking agents, not a tenant pod. No crash or privilege escalation is described.

Who can reach it

Local, requires the privilege to load XDP/BPF programs on the node (CAP_BPF plus CAP_NET_ADMIN), so realistically a node agent or an operator with a custom datapath program. Not reachable by an unprivileged tenant unless BPF load has been delegated.

What to do

Update to a stable kernel carrying the corrected prototype (five stable commits linked, matching bpf_skb_store_bytes) and reboot the node; folding it into the regular kernel rollout is appropriate. No separate mitigation exists, though not delegating BPF program loading to tenants removes the exposure.

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.