CVE-2024-47702

published 21 Oct 2024 · updated 3 Oct 2026

bpf: Fail verification for sign-extension of packet data/data_end/data_meta

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4b48228eebce2ab1b01e3133da822164472b7e46, Kernel 92de36080c93296ef9005690705cba260b9bd68a, Kernel f09757fe97a225ae505886eac572e4cbfba96537 and 1 more.

In the Linux kernel, the following vulnerability has been resolved: bpf: Fail verification for sign-extension of packet data/data_end/data_meta syzbot reported a kernel crash due to commit 1f1e864b6555 ("bpf: Handle sign-extenstin ctx member accesses"). The reason is due to sign-extension of 32-bit load for packet data/data_end/data_meta uapi field. The original code looks like: r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ r3 = *(u32 *)(r1 + 80) /* load __sk_buff->data_end */ r0 = r2 r0 += 8 if r3 > r0 goto +1 ... Note that __sk_buff->data load has 32-bit sign extension. After verification and convert_ctx_accesses(), the final asm code looks like: r2 = *(u64 *)(r1 +208) r2 = (s32)r2 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 ... Note that 'r2 = (s32)r2' may make the kernel __sk_buff->data address invalid which may cause runtime failure. Currently, in C code, typically we have void *data = (void *)(long)skb->data; void *data_end = (void *)(long)skb->data_end; ... and it will generate r2 = *(u64 *)(r1 +208) r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 If we allow sign-extension, void *data = (void *)(long)(int)skb->data; void *data_end = (void *)(long)skb->data_end; ... the generated code looks like r2 = *(u64 *)(r1 +208) r2 <<= 32 r2 s>>= 32 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 and this will cause verification failure since "r2 <<= 32" is not allowed as "r2" is a packet pointer. To fix this issue for case r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ this patch added additional checking in is_valid_access() callback function for packet data/data_end/data_meta access. If those accesses are with sign-extenstion, the verification will fail. [1] https://lore.kernel.org/bpf/000000000000c90eee061d236d37@google.com/

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.6, >=1f1e864b65554e33fe74e3377e58b12f4302f2eb <4b48228eebce2ab1b01e3133da822164472b7e46, >=1f1e864b65554e33fe74e3377e58b12f4302f2eb <92de36080c93296ef9005690705cba260b9bd68a, >=1f1e864b65554e33fe74e3377e58b12f4302f2eb <f09757fe97a225ae505886eac572e4cbfba96537, >=1f1e864b65554e33fe74e3377e58b12f4302f2eb <f1620c93a1ec950d87ef327a565d3907736d33404b48228eebce2ab1b01e3133da822164472b7e46, 92de36080c93296ef9005690705cba260b9bd68a, f09757fe97a225ae505886eac572e4cbfba96537, f1620c93a1ec950d87ef327a565d3907736d3340

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-47702 severity on Zeptric[![CVE-2024-47702](https://zeptric.io/badge/cve/CVE-2024-47702.svg)](https://zeptric.io/cve/CVE-2024-47702)