CVE-2026-53366

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-16. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 6 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
5.2%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 22, 2026

Advisory Details (5)

Auto-updated Jul 18, 2026
No patch confirmed yet.
generic

ipv4: account for fraggap on the paged allocation path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eca856950f7cb1a221e02b99d758409f2c5cec42
generic

ipv4: account for fraggap on the paged allocation path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c04d9ece23deb9e26c19f9ca215e98b3295aa1bb
generic

ipv4: account for fraggap on the paged allocation path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/77798d7be6ef71e72fb6fc8a2901bf74ebc9706f
generic

ipv4: account for fraggap on the paged allocation path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a9c24eda24bd15f432e37824e6fc440977cb241c
generic

ipv4: account for fraggap on the paged allocation path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ce494707a9c07f27c219ca67f3e138061f53d9b3

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-55.86.1.el10_02026-07-06redhat
redhatkernel-0:6.12.0-211.30.1.el10_22026-07-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Data Freshness Timeline

(refreshed 20× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:19 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:35 UTCEG score recompute
  8. 2026-07-19 02:35 UTCVendor advisory
  9. 2026-07-19 02:35 UTCGHSA enrichment
  10. 2026-07-19 02:29 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-18 08:00 UTCEG score recompute 7.80
  13. 2026-07-18 08:00 UTCGHSA enrichment
  14. 2026-07-18 07:59 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  15. 2026-07-17 07:04 UTCEG score recompute
  16. 2026-07-17 07:04 UTCGHSA enrichment
  17. 2026-07-16 17:03 UTCEPSS rescore
  18. 2026-07-16 06:26 UTCNVD update
  19. 2026-07-16 05:29 UTCEG score recompute
  20. 2026-07-16 05:28 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53366?
CVE-2026-53366 is a high vulnerability published on July 16, 2026. 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;…
When was CVE-2026-53366 disclosed?
CVE-2026-53366 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53366 actively exploited?
CVE-2026-53366 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53366?
CVE-2026-53366 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53366?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53366, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53366

Explore →

Is Your Infrastructure Affected by CVE-2026-53366?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.