CVE-2026-53366: ipv4: account for fraggap on the paged allocation path
In the Linux kernel, the following vulnerability has been resolved:
ipv4: account for fraggap on the paged allocation path
In ipappenddata(), 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 skbcopyandcsumbits(). 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.150.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53366?
The severity of CVE-2026-53366 is high, with a CVSS score of 7.8.
How do I fix CVE-2026-53366?
To mitigate CVE-2026-53366, update the Linux kernel to the version that incorporates the fix for this vulnerability.
What systems are affected by CVE-2026-53366?
CVE-2026-53366 affects the Linux kernel on systems that utilize IPv4 network functionalities.
What type of vulnerability is CVE-2026-53366?
CVE-2026-53366 is a memory allocation vulnerability within the IP data append process in the Linux kernel.
Is CVE-2026-53366 easy to exploit?
CVE-2026-53366 has a low access vector but is classified as high severity due to its potential impact on system confidentiality, integrity, and availability.