Answer in brief
CVE-2026-53366 records a Unknown severity vulnerability in ipv4: account for fraggap on the paged allocation path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8eb77cc73977d88787b37c92831b1c242e035396 <5c6375bced6147ec2e460ee3b653f4860d5ecdc2 || >=8eb77cc73977d88787b37c92831b1c242e035396 <ce494707a9c07f27c219ca67f3e138061f53d9b3 || >=8eb77cc73977d88787b37c92831b1c242e035396 <a9c24eda24bd15f432e37824e6fc440977cb241c || >=8eb77cc73977d88787b37c92831b1c242e035396 <77798d7be6ef71e72fb6fc8a2901bf74ebc9706f || >=8eb77cc73977d88787b37c92831b1c242e035396 <c04d9ece23deb9e26c19f9ca215e98b3295aa1bb || >=8eb77cc73977d88787b37c92831b1c242e035396 <eca856950f7cb1a221e02b99d758409f2c5cec42 | 5c6375bced6147ec2e460ee3b653f4860d5ecdc2, ce494707a9c07f27c219ca67f3e138061f53d9b3, a9c24eda24bd15f432e37824e6fc440977cb241c, 77798d7be6ef71e72fb6fc8a2901bf74ebc9706f, c04d9ece23deb9e26c19f9ca215e98b3295aa1bb, eca856950f7cb1a221e02b99d758409f2c5cec42 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Jul 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-53366 records a Unknown severity vulnerability in ipv4: account for fraggap on the paged allocation path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8eb77cc73977d88787b37c92831b1c242e035396 <5c6375bced6147ec2e460ee3b653f4860d5ecdc2 || >=8eb77cc73977d88787b37c92831b1c242e035396 <ce494707a9c07f27c219ca67f3e138061f53d9b3 || >=8eb77cc73977d88787b37c92831b1c242e035396 <a9c24eda24bd15f432e37824e6fc440977cb241c || >=8eb77cc73977d88787b37c92831b1c242e035396 <77798d7be6ef71e72fb6fc8a2901bf74ebc9706f || >=8eb77cc73977d88787b37c92831b1c242e035396 <c04d9ece23deb9e26c19f9ca215e98b3295aa1bb || >=8eb77cc73977d88787b37c92831b1c242e035396 <eca856950f7cb1a221e02b99d758409f2c5cec42 | 5c6375bced6147ec2e460ee3b653f4860d5ecdc2, ce494707a9c07f27c219ca67f3e138061f53d9b3, a9c24eda24bd15f432e37824e6fc440977cb241c, 77798d7be6ef71e72fb6fc8a2901bf74ebc9706f, c04d9ece23deb9e26c19f9ca215e98b3295aa1bb, eca856950f7cb1a221e02b99d758409f2c5cec42 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Jul 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.