GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel sockmap: bpf_msg_push_data mis-advances split fragment offset, corrupting scatterlist layout

CVSS 8.4CVE-2026-63926Kernel, userspace & hypervisorcurated

Impact

When bpf_msg_push_data() inserts data in the middle of a scatterlist entry it splits the entry, but advances the right fragment's page-local offset by the message-global insertion point. For inserts into any entry other than the first, the offset over-advances and the resulting split layout is inconsistent, giving memory corruption potential in the socket message path. This lives in the sockmap/sk_msg path, which is reached by BPF programs attached to sockets - exactly the mechanism service meshes, sidecar-free L7 proxies and Cilium-style datapaths use on Kubernetes GPU nodes. A tenant or workload able to load such a program, or a bug in the cluster's own datapath program, can destabilize the host kernel on a node that is expensive to drain.

Who can reach it

Local: requires the ability to load and attach a BPF sockmap program (CAP_BPF/CAP_NET_ADMIN or an unprivileged-BPF-permissive configuration), then send traffic through the attached socket. Not remotely reachable on its own.

What to do

Apply the stable kernel update that advances the fragment offset by the fragment-local delta (five stable branches carry the fix; see the git.kernel.org commits). Reboot each affected node, or use livepatching if your distribution ships it for this commit. Until patched, the exposure is limited by who can attach sockmap programs - keep unprivileged BPF disabled and restrict CAP_BPF to the cluster datapath, not tenant workloads.

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.