# CVE-2024-50258: net: fix crash when config small gso_max_size/gso_ipv4_max_size

> A local attacker can cause a kernel crash by configuring small GSO max sizes, leading to an integer underflow and subsequent BUG_ON trigger.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Nov 2024
- **Updated:** 11 May 2026
- **Also known as:** AZL-53333, AZL-53361, BELL-CVE-2024-50258, DEBIAN-CVE-2024-50258, GHSA-4qfr-cjvm-qrcj, ROOT-OS-DEBIAN-11-CVE-2024-50258, ROOT-OS-UBUNTU-2204-CVE-2024-50258, UBUNTU-CVE-2024-50258

## What is CVE-2024-50258?

CVE-2024-50258 is a medium-severity vulnerability in Linux kernel, published on 9 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound))

## Which versions are affected by CVE-2024-50258?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-50258?

Apply the vendor's patch.

## Is CVE-2024-50258 being exploited?

There is no known exploitation of CVE-2024-50258 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50258 and fix it if it is affected.

What it is: CVE-2024-50258 is a medium-severity vulnerability in Linux kernel, published on 9 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50258 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-50258/ (Markdown: https://insights.sbomify.com/CVE-2024-50258/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-50258
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-50258
- OSV: https://osv.dev/vulnerability/CVE-2024-50258

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-50258/
Summaries are generated and may contain mistakes; the official description above is the record.