| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-47702: bpf: Fail verification for sign-extension of packet data/data_end/data_meta |
| |
| Description |
| =========== |
| |
| 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/ |
| |
| The Linux kernel CVE team has assigned CVE-2024-47702 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.6 with commit 1f1e864b65554e33fe74e3377e58b12f4302f2eb and fixed in 6.10.13 with commit f1620c93a1ec950d87ef327a565d3907736d3340 |
| Issue introduced in 6.6 with commit 1f1e864b65554e33fe74e3377e58b12f4302f2eb and fixed in 6.11.2 with commit f09757fe97a225ae505886eac572e4cbfba96537 |
| Issue introduced in 6.6 with commit 1f1e864b65554e33fe74e3377e58b12f4302f2eb and fixed in 6.12 with commit 92de36080c93296ef9005690705cba260b9bd68a |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2024-47702 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| include/linux/bpf.h |
| kernel/bpf/verifier.c |
| net/core/filter.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/f1620c93a1ec950d87ef327a565d3907736d3340 |
| https://git.kernel.org/stable/c/f09757fe97a225ae505886eac572e4cbfba96537 |
| https://git.kernel.org/stable/c/92de36080c93296ef9005690705cba260b9bd68a |