CVE-2026-80793

ipv4: reject undersized MTUs in ip_do_fragment()

N/A
Published: September 4, 2026 at 03:13 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Vendor states this is fixed in 3556beb8ca86677af2aca5bfbed6f8e790fccc83 (fixed)
Vendor states this is fixed in 36e0741833bd823866f8cb9f112f37cea1a70b60 (fixed)
Vendor states this is fixed in 515b6816ba0c12d8415c88e5f41e6ec029e35cfa (fixed)
Vendor states this is fixed in 74ce7389f8f562d39015f59a00ef7ad6acd37803 (fixed)
Vendor states this is fixed in a716a64a4ba68cd46f2745fba2b1099fe8e0aa59 (fixed)
Vendor states this is fixed in b0ea911453ce7210e8200a07a94d2458bd1e6430 (fixed)
Vendor states this is fixed in c0726f0caf8c6b3208552949e17d23634a2f3129 (fixed)
Vendor states this is fixed in c8a74adccaf028223054633b532593101dfcc581 (fixed)
Vendor states this is fixed in d9d1a676b033acabf8e5645f730486d1f8204a3f (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15.218 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.106 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 6.6.154 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card