CVE-2026-80793
ipv4: reject undersized MTUs in ip_do_fragment()
Reported by linux · Published September 4, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.12-devel | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| bpftool6.18 | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| kernel6.12-headers | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| kernel6.12 | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| kernel6.12-tools-devel | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| perf6.18 | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 |
| Linux | Linux | 2.6.12, 0, 5.10.267 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | perf6.18 | 0 |
| linux | linux_kernel | 2.6.12, 2.6.12, 2.6.12 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | bpftool | 0 |
| amazon:2023 | bpftool6.12 | 0 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| amazon:2023 | kernel-livepatch-6.18.48-107.148 | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | microvm-kernel6.18 | 0 |
| amazon:2023 | python3-perf | 0 |
…and 18 more
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (12 in total, the first dated here)
- Sep 15, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80793
vulnetix vdb fixes CVE-2026-80793
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80793/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart