| 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-2022-49209: bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full |
| |
| If tcp_bpf_sendmsg() is running while sk msg is full. When sk_msg_alloc() |
| returns -ENOMEM error, tcp_bpf_sendmsg() goes to wait_for_memory. If partial |
| memory has been alloced by sk_msg_alloc(), that is, msg_tx->sg.size is |
| greater than osize after sk_msg_alloc(), memleak occurs. To fix we use |
| sk_msg_trim() to release the allocated memory, then goto wait for memory. |
| |
| Other call paths of sk_msg_alloc() have the similar issue, such as |
| tls_sw_sendmsg(), so handle sk_msg_trim logic inside sk_msg_alloc(), |
| as Cong Wang suggested. |
| |
| This issue can cause the following info: |
| WARNING: CPU: 3 PID: 7950 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0 |
| Call Trace: |
| <TASK> |
| inet_csk_destroy_sock+0x55/0x110 |
| __tcp_close+0x279/0x470 |
| tcp_close+0x1f/0x60 |
| inet_release+0x3f/0x80 |
| __sock_release+0x3d/0xb0 |
| sock_close+0x11/0x20 |
| __fput+0x92/0x250 |
| task_work_run+0x6a/0xa0 |
| do_exit+0x33b/0xb60 |
| do_group_exit+0x2f/0xa0 |
| get_signal+0xb6/0x950 |
| arch_do_signal_or_restart+0xac/0x2a0 |
| exit_to_user_mode_prepare+0xa9/0x200 |
| syscall_exit_to_user_mode+0x12/0x30 |
| do_syscall_64+0x46/0x80 |
| entry_SYSCALL_64_after_hwframe+0x44/0xae |
| </TASK> |
| |
| WARNING: CPU: 3 PID: 2094 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260 |
| Call Trace: |
| <TASK> |
| __sk_destruct+0x24/0x1f0 |
| sk_psock_destroy+0x19b/0x1c0 |
| process_one_work+0x1b3/0x3c0 |
| kthread+0xe6/0x110 |
| ret_from_fork+0x22/0x30 |
| </TASK> |
| |
| The Linux kernel CVE team has assigned CVE-2022-49209 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.20 with commit 604326b41a6fb9b4a78b6179335decee0365cd8c and fixed in 5.4.189 with commit 6d03722c34d9603df325f67c6d30dc1b7b3c6067 |
| Issue introduced in 4.20 with commit 604326b41a6fb9b4a78b6179335decee0365cd8c and fixed in 5.10.110 with commit bec34a91eba3483e1830c02bdd36f8f968642047 |
| Issue introduced in 4.20 with commit 604326b41a6fb9b4a78b6179335decee0365cd8c and fixed in 5.15.33 with commit de3a8d8fab0710186f7864ec812836d8d70da3c9 |
| Issue introduced in 4.20 with commit 604326b41a6fb9b4a78b6179335decee0365cd8c and fixed in 5.16.19 with commit f677328f05f52d535cbdc15cb04476db49477eb4 |
| Issue introduced in 4.20 with commit 604326b41a6fb9b4a78b6179335decee0365cd8c and fixed in 5.17.2 with commit d0b85dfc6f01d26808e2576c6537c131b590e270 |
| Issue introduced in 4.20 with commit 604326b41a6fb9b4a78b6179335decee0365cd8c and fixed in 5.18 with commit 9c34e38c4a870eb30b13f42f5b44f42e9d19ccb8 |
| |
| 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-49209 |
| 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: |
| net/core/skmsg.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/6d03722c34d9603df325f67c6d30dc1b7b3c6067 |
| https://git.kernel.org/stable/c/bec34a91eba3483e1830c02bdd36f8f968642047 |
| https://git.kernel.org/stable/c/de3a8d8fab0710186f7864ec812836d8d70da3c9 |
| https://git.kernel.org/stable/c/f677328f05f52d535cbdc15cb04476db49477eb4 |
| https://git.kernel.org/stable/c/d0b85dfc6f01d26808e2576c6537c131b590e270 |
| https://git.kernel.org/stable/c/9c34e38c4a870eb30b13f42f5b44f42e9d19ccb8 |
