cve/2024/CVE-2024-50258.md

### [CVE-2024-50258](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50258)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=4.16%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=46e6b992c2502b094e61da6994f1363f3b7c1413%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=blue)

### Description

In the Linux kernel, the following vulnerability has been resolved:net: fix crash when config small gso_max_size/gso_ipv4_max_sizeConfig a small gso_max_size/gso_ipv4_max_size will lead to an underflowin 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.

### POC

#### Reference
No PoCs from references.

#### Github
- https://github.com/w4zu/Debian_security