CVE-2024-50258
Severity CVSS v4.0:
Pending analysis
Type:
CWE-191
Integer Underflow (Wrap or Wraparound)
Publication date:
09/11/2024
Last modified:
03/11/2025
Description
In the Linux kernel, the following vulnerability has been resolved:<br />
<br />
net: fix crash when config small gso_max_size/gso_ipv4_max_size<br />
<br />
Config a small gso_max_size/gso_ipv4_max_size will lead to an underflow<br />
in sk_dst_gso_max_size(), which may trigger a BUG_ON crash,<br />
because sk->sk_gso_max_size would be much bigger than device limits.<br />
Call Trace:<br />
tcp_write_xmit<br />
tso_segs = tcp_init_tso_segs(skb, mss_now);<br />
tcp_set_skb_tso_segs<br />
tcp_skb_pcount_set<br />
// skb->len = 524288, mss_now = 8<br />
// u16 tso_segs = 524288/8 = 65535 -> 0<br />
tso_segs = DIV_ROUND_UP(skb->len, mss_now)<br />
BUG_ON(!tso_segs)<br />
Add check for the minimum value of gso_max_size and gso_ipv4_max_size.
Impact
Base Score 3.x
5.50
Severity 3.x
MEDIUM
Vulnerable products and versions
| CPE | From | Up to |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 4.16 (including) | 6.6.60 (including) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 6.7 (including) | 6.11.7 (including) |
| cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:* | ||
| cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:* | ||
| cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:* | ||
| cpe:2.3:o:linux:linux_kernel:6.12:rc4:*:*:*:*:*:* | ||
| cpe:2.3:o:linux:linux_kernel:6.12:rc5:*:*:*:*:*:* |
To consult the complete list of CPE names with products and versions, see this page
References to Advisories, Solutions, and Tools
- https://git.kernel.org/stable/c/90c8482a5d9791259ba77bfdc1849fc5128b4be7
- https://git.kernel.org/stable/c/9ab5cf19fb0e4680f95e506d6c544259bf1111c4
- https://git.kernel.org/stable/c/ac5977001eee7660c643f8e07a2de9001990b7b8
- https://git.kernel.org/stable/c/e72fd1389a5364bc6aa6312ecf30bdb5891b9486
- https://git.kernel.org/stable/c/e9365368b483328639c03fc730448dccd5a25b6b
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html



