| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2021-47376: bpf: Add oversize check before call kvcalloc() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| bpf: Add oversize check before call kvcalloc() |
| |
| Commit 7661809d493b ("mm: don't allow oversized kvmalloc() calls") add the |
| oversize check. When the allocation is larger than what kmalloc() supports, |
| the following warning triggered: |
| |
| WARNING: CPU: 0 PID: 8408 at mm/util.c:597 kvmalloc_node+0x108/0x110 mm/util.c:597 |
| Modules linked in: |
| CPU: 0 PID: 8408 Comm: syz-executor221 Not tainted 5.14.0-syzkaller #0 |
| Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 |
| RIP: 0010:kvmalloc_node+0x108/0x110 mm/util.c:597 |
| Call Trace: |
| kvmalloc include/linux/mm.h:806 [inline] |
| kvmalloc_array include/linux/mm.h:824 [inline] |
| kvcalloc include/linux/mm.h:829 [inline] |
| check_btf_line kernel/bpf/verifier.c:9925 [inline] |
| check_btf_info kernel/bpf/verifier.c:10049 [inline] |
| bpf_check+0xd634/0x150d0 kernel/bpf/verifier.c:13759 |
| bpf_prog_load kernel/bpf/syscall.c:2301 [inline] |
| __sys_bpf+0x11181/0x126e0 kernel/bpf/syscall.c:4587 |
| __do_sys_bpf kernel/bpf/syscall.c:4691 [inline] |
| __se_sys_bpf kernel/bpf/syscall.c:4689 [inline] |
| __x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4689 |
| do_syscall_x64 arch/x86/entry/common.c:50 [inline] |
| do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 |
| entry_SYSCALL_64_after_hwframe+0x44/0xae |
| |
| The Linux kernel CVE team has assigned CVE-2021-47376 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.0 with commit c454a46b5efd8eff8880e88ece2976e60a26bf35 and fixed in 5.4.150 with commit 93937596e0652d50973f9dc944fea1694ac8cdfd |
| Issue introduced in 5.0 with commit c454a46b5efd8eff8880e88ece2976e60a26bf35 and fixed in 5.10.70 with commit 6345a0bee80139ea00a341c4202ebfd1534b5eb0 |
| Issue introduced in 5.0 with commit c454a46b5efd8eff8880e88ece2976e60a26bf35 and fixed in 5.14.9 with commit b5fe7cdfee5901ce5513c30e554d51536e003bde |
| Issue introduced in 5.0 with commit c454a46b5efd8eff8880e88ece2976e60a26bf35 and fixed in 5.15 with commit 0e6491b559704da720f6da09dd0a52c4df44c514 |
| |
| 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-2021-47376 |
| 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: |
| kernel/bpf/verifier.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/93937596e0652d50973f9dc944fea1694ac8cdfd |
| https://git.kernel.org/stable/c/6345a0bee80139ea00a341c4202ebfd1534b5eb0 |
| https://git.kernel.org/stable/c/b5fe7cdfee5901ce5513c30e554d51536e003bde |
| https://git.kernel.org/stable/c/0e6491b559704da720f6da09dd0a52c4df44c514 |
