| 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-53187: io_uring: check for overflows in io_pin_pages |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| io_uring: check for overflows in io_pin_pages |
| |
| WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144 |
| CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0 |
| Call Trace: |
| <TASK> |
| __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183 |
| io_rings_map io_uring/io_uring.c:2611 [inline] |
| io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470 |
| io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692 |
| io_uring_setup io_uring/io_uring.c:3781 [inline] |
| ... |
| </TASK> |
| |
| io_pin_pages()'s uaddr parameter came directly from the user and can be |
| garbage. Don't just add size to it as it can overflow. |
| |
| The Linux kernel CVE team has assigned CVE-2024-53187 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.1 with commit 2b188cc1bb857a9d4701ae59aa7768b5124e262e and fixed in 6.11.11 with commit 29eac3eca72d4c2a71122050c37cd7d8f73ac4f3 |
| Issue introduced in 5.1 with commit 2b188cc1bb857a9d4701ae59aa7768b5124e262e and fixed in 6.12.2 with commit aaa90844afd499c9142d0199dfda74439314c013 |
| Issue introduced in 5.1 with commit 2b188cc1bb857a9d4701ae59aa7768b5124e262e and fixed in 6.13 with commit 0c0a4eae26ac78379d0c1db053de168a8febc6c9 |
| |
| 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-53187 |
| 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: |
| io_uring/memmap.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/29eac3eca72d4c2a71122050c37cd7d8f73ac4f3 |
| https://git.kernel.org/stable/c/aaa90844afd499c9142d0199dfda74439314c013 |
| https://git.kernel.org/stable/c/0c0a4eae26ac78379d0c1db053de168a8febc6c9 |
