| 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-2024-50258: net: fix crash when config small gso_max_size/gso_ipv4_max_size |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| net: fix crash when config small gso_max_size/gso_ipv4_max_size |
| |
| Config a small gso_max_size/gso_ipv4_max_size will lead to an underflow |
| in sk_dst_gso_max_size(), which may trigger a BUG_ON crash, |
| because sk->sk_gso_max_size would be much bigger than device limits. |
| Call Trace: |
| tcp_write_xmit |
| tso_segs = tcp_init_tso_segs(skb, mss_now); |
| tcp_set_skb_tso_segs |
| tcp_skb_pcount_set |
| // skb->len = 524288, mss_now = 8 |
| // u16 tso_segs = 524288/8 = 65535 -> 0 |
| tso_segs = DIV_ROUND_UP(skb->len, mss_now) |
| BUG_ON(!tso_segs) |
| Add check for the minimum value of gso_max_size and gso_ipv4_max_size. |
| |
| The Linux kernel CVE team has assigned CVE-2024-50258 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.16 with commit 46e6b992c2502b094e61da6994f1363f3b7c1413 and fixed in 5.15.181 with commit 90c8482a5d9791259ba77bfdc1849fc5128b4be7 |
| Issue introduced in 4.16 with commit 46e6b992c2502b094e61da6994f1363f3b7c1413 and fixed in 6.1.120 with commit e9365368b483328639c03fc730448dccd5a25b6b |
| Issue introduced in 4.16 with commit 46e6b992c2502b094e61da6994f1363f3b7c1413 and fixed in 6.6.60 with commit ac5977001eee7660c643f8e07a2de9001990b7b8 |
| Issue introduced in 4.16 with commit 46e6b992c2502b094e61da6994f1363f3b7c1413 and fixed in 6.11.7 with commit e72fd1389a5364bc6aa6312ecf30bdb5891b9486 |
| Issue introduced in 4.16 with commit 46e6b992c2502b094e61da6994f1363f3b7c1413 and fixed in 6.12 with commit 9ab5cf19fb0e4680f95e506d6c544259bf1111c4 |
| |
| 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-50258 |
| 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/rtnetlink.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/90c8482a5d9791259ba77bfdc1849fc5128b4be7 |
| https://git.kernel.org/stable/c/e9365368b483328639c03fc730448dccd5a25b6b |
| https://git.kernel.org/stable/c/ac5977001eee7660c643f8e07a2de9001990b7b8 |
| https://git.kernel.org/stable/c/e72fd1389a5364bc6aa6312ecf30bdb5891b9486 |
| https://git.kernel.org/stable/c/9ab5cf19fb0e4680f95e506d6c544259bf1111c4 |
