GPU VulnDB

Database/Kernel, userspace & hypervisor

PREVAIL eBPF verifier: stale offset tracking lets out-of-bounds BPF programs pass verification

CVSS 9.3CVE-2026-53670Kernel, userspace & hypervisorcurated

Impact

PREVAIL's abstract interpreter silently skips offset-variable updates when the destination register holds a non-singleton typeset, so later bounds checks run against a stale offset and accept memory accesses that are out of bounds at runtime. Anything that relies on PREVAIL as its safety gate before loading BPF bytecode - the verifier is used outside the Linux in-kernel verifier, notably in eBPF-for-Windows and in tooling that pre-screens programs - can be handed a crafted program that passes review and then corrupts memory in the execution context. Where a fleet uses PREVAIL to admit tenant- or third-party-supplied BPF for observability or networking, the admission decision cannot be trusted. This does not affect the in-kernel Linux verifier, which is separate code.

Who can reach it

Anyone who can submit a BPF program to a component that uses PREVAIL for verification. Reach depends entirely on the deployment - it is only exposed where untrusted bytecode is accepted.

What to do

Update PREVAIL to 0.2.4 and rebuild or update whatever embeds it, then restart the affected component. There is no configuration mitigation for the verifier logic itself; until the dependency is updated, stop accepting BPF programs from untrusted sources on that path.

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.