GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel BPF verifier: writes through untrusted BTF pointers bypass the read-only policy

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

Impact

check_ptr_to_btf_access() let a program type's btf_struct_access callback validate a write before the default BTF path could reject non-read accesses. That bypassed the read-only policy that is supposed to apply to untrusted BTF pointers, such as those produced by bpf_rdonly_cast(). A loaded program could therefore write through a pointer the verifier had already decided it must not trust, giving kernel memory corruption of attacker-chosen targets. This is a different hole from the size-truncation and MEM_ALLOC bounds bugs in the same batch - it is a policy-ordering mistake, not a bound arithmetic mistake - so verify your kernel carries all three fixes rather than assuming one backport covers them.

Who can reach it

Local user or container that can load BPF programs (CAP_BPF/CAP_SYS_ADMIN in a namespace) and call bpf_rdonly_cast() or a similar untrusted-pointer helper. Unreachable where BPF program loading is denied to tenants.

What to do

Update to a stable kernel containing the fix that rejects non-read accesses through PTR_UNTRUSTED BTF pointers at the common entry point before the callback branch; commits are in the record. Kernel package update plus drain and reboot of each affected node; no vendor mitigation short of removing BPF load capability from 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.