| From bippy-1.1.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-2022-49791: io_uring: fix multishot accept request leaks |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| io_uring: fix multishot accept request leaks |
| |
| Having REQ_F_POLLED set doesn't guarantee that the request is |
| executed as a multishot from the polling path. Fortunately for us, if |
| the code thinks it's multishot issue when it's not, it can only ask to |
| skip completion so leaking the request. Use issue_flags to mark |
| multipoll issues. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49791 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.19 with commit 390ed29b5e425ba00da2b6113b74a14949f71b02 and fixed in 6.0.10 with commit 0e4626de856ef8f25ecd9c716e76d4f95ce95639 |
| Issue introduced in 5.19 with commit 390ed29b5e425ba00da2b6113b74a14949f71b02 and fixed in 6.1 with commit 91482864768a874c4290ef93b84a78f4f1dac51b |
| |
| 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-2022-49791 |
| 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/io_uring.h |
| io_uring/io_uring.c |
| io_uring/io_uring.h |
| io_uring/net.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/0e4626de856ef8f25ecd9c716e76d4f95ce95639 |
| https://git.kernel.org/stable/c/91482864768a874c4290ef93b84a78f4f1dac51b |
