| 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-2021-47607: bpf: Fix kernel address leakage in atomic cmpxchg's r0 aux reg |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| bpf: Fix kernel address leakage in atomic cmpxchg's r0 aux reg |
| |
| The implementation of BPF_CMPXCHG on a high level has the following parameters: |
| |
| .-[old-val] .-[new-val] |
| BPF_R0 = cmpxchg{32,64}(DST_REG + insn->off, BPF_R0, SRC_REG) |
| `-[mem-loc] `-[old-val] |
| |
| Given a BPF insn can only have two registers (dst, src), the R0 is fixed and |
| used as an auxilliary register for input (old value) as well as output (returning |
| old value from memory location). While the verifier performs a number of safety |
| checks, it misses to reject unprivileged programs where R0 contains a pointer as |
| old value. |
| |
| Through brute-forcing it takes about ~16sec on my machine to leak a kernel pointer |
| with BPF_CMPXCHG. The PoC is basically probing for kernel addresses by storing the |
| guessed address into the map slot as a scalar, and using the map value pointer as |
| R0 while SRC_REG has a canary value to detect a matching address. |
| |
| Fix it by checking R0 for pointers, and reject if that's the case for unprivileged |
| programs. |
| |
| The Linux kernel CVE team has assigned CVE-2021-47607 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.12 with commit 5ffa25502b5ab3d639829a2d1e316cff7f59a41e and fixed in 5.15.11 with commit f87a6c160ecc8c7b417d25f508d3f076fe346136 |
| Issue introduced in 5.12 with commit 5ffa25502b5ab3d639829a2d1e316cff7f59a41e and fixed in 5.16 with commit a82fe085f344ef20b452cd5f481010ff96b5c4cd |
| |
| 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-47607 |
| 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/f87a6c160ecc8c7b417d25f508d3f076fe346136 |
| https://git.kernel.org/stable/c/a82fe085f344ef20b452cd5f481010ff96b5c4cd |