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

Published Jul 16, 2026
·
Updated

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

6 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=6.0<6.6.144
Linux Linux kernel>=6.7<6.12.95
Linux Linux kernel>=6.13<6.18.38
Linux Linux kernel>=6.19<7.1.3
Microsoft azl3 kernel 6.6.143.1-1<6.6.150.1-1
6.6.150.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.150.1-1

Event History

Jul 16, 2026
CVE Published
via MITRE·05:13 AM
Data Sourced
via MITRE·05:13 AM
DescriptionSeverity
Data Sourced
via NVD·06:16 AM
RemedyDescriptionSeverityAffected Software
Jul 17, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:01 AM
Affected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
Aug 21, 58589
Event
via Microsoft·04:15 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-53366?

The severity of CVE-2026-53366 is high, with a CVSS score of 7.8.

2

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.

3

What systems are affected by CVE-2026-53366?

CVE-2026-53366 affects the Linux kernel on systems that utilize IPv4 network functionalities.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203