CVE-2026-53366

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM 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 — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 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(medium)
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 PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 16, 2026

Last Modified

August 17, 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(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-08ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-08ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-08ubuntu
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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.3-1

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 114× 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.

Showing the most recent 100 of 238 total refreshes for this CVE.

  1. 2026-09-10 09:35 UTCEPSS rescore
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-08 00:37 UTCEG score recompute
  4. 2026-09-08 00:37 UTCVendor advisory
  5. 2026-09-08 00:37 UTCGHSA enrichment
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:27 UTCVendor advisory
  9. 2026-09-06 13:27 UTCGHSA enrichment
  10. 2026-09-05 20:43 UTCEG score recompute
  11. 2026-09-05 20:43 UTCVendor advisory
  12. 2026-09-05 20:43 UTCGHSA enrichment
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-31 04:48 UTCEG score recompute
  17. 2026-08-31 04:48 UTCVendor advisory
  18. 2026-08-31 04:48 UTCGHSA enrichment
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 16:14 UTCVendor advisory
  21. 2026-08-30 16:14 UTCGHSA enrichment
  22. 2026-08-30 03:40 UTCEG score recompute
  23. 2026-08-30 03:40 UTCVendor advisory
  24. 2026-08-30 03:40 UTCGHSA enrichment
  25. 2026-08-30 01:22 UTCEPSS rescore
Show 75 more
  1. 2026-08-28 21:41 UTCEPSS rescore
  2. 2026-08-28 02:28 UTCEG score recompute
  3. 2026-08-28 02:28 UTCVendor advisory
  4. 2026-08-28 02:28 UTCGHSA enrichment
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-27 13:54 UTCVendor advisory
  7. 2026-08-27 13:54 UTCGHSA enrichment
  8. 2026-08-27 01:20 UTCEG score recompute
  9. 2026-08-27 01:20 UTCVendor advisory
  10. 2026-08-27 01:20 UTCGHSA enrichment
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-26 12:45 UTCVendor advisory
  13. 2026-08-26 12:44 UTCGHSA enrichment
  14. 2026-08-25 23:51 UTCEG score recompute
  15. 2026-08-25 23:51 UTCVendor advisory
  16. 2026-08-25 23:51 UTCGHSA enrichment
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-25 08:47 UTCVendor advisory
  19. 2026-08-25 08:47 UTCGHSA enrichment
  20. 2026-08-24 19:31 UTCEG score recompute
  21. 2026-08-24 19:31 UTCVendor advisory
  22. 2026-08-24 19:31 UTCGHSA enrichment
  23. 2026-08-24 04:57 UTCVendor advisory
  24. 2026-08-24 04:57 UTCGHSA enrichment
  25. 2026-08-23 16:23 UTCVendor advisory
  26. 2026-08-23 16:23 UTCGHSA enrichment
  27. 2026-08-23 03:48 UTCEG score recompute
  28. 2026-08-23 03:48 UTCVendor advisory
  29. 2026-08-23 03:48 UTCGHSA enrichment
  30. 2026-08-23 00:19 UTCEPSS rescore
  31. 2026-08-22 15:14 UTCVendor advisory
  32. 2026-08-22 15:14 UTCGHSA enrichment
  33. 2026-08-22 02:39 UTCEG score recompute
  34. 2026-08-22 02:39 UTCVendor advisory
  35. 2026-08-22 02:39 UTCGHSA enrichment
  36. 2026-08-21 23:49 UTCEPSS rescore
  37. 2026-08-21 14:03 UTCVendor advisory
  38. 2026-08-21 14:03 UTCGHSA enrichment
  39. 2026-08-21 01:13 UTCEG score recompute
  40. 2026-08-21 01:13 UTCVendor advisory
  41. 2026-08-21 01:12 UTCGHSA enrichment
  42. 2026-08-20 22:55 UTCEPSS rescore
  43. 2026-08-20 12:38 UTCVendor advisory
  44. 2026-08-20 12:38 UTCGHSA enrichment
  45. 2026-08-20 00:04 UTCEG score recompute
  46. 2026-08-20 00:04 UTCVendor advisory
  47. 2026-08-20 00:04 UTCGHSA enrichment
  48. 2026-08-19 17:04 UTCEPSS rescore
  49. 2026-08-19 11:08 UTCVendor advisory
  50. 2026-08-19 11:08 UTCGHSA enrichment
  51. 2026-08-18 22:32 UTCEG score recompute
  52. 2026-08-18 22:32 UTCVendor advisory
  53. 2026-08-18 22:32 UTCGHSA enrichment
  54. 2026-08-18 13:48 UTCEPSS rescore
  55. 2026-08-18 09:58 UTCVendor advisory
  56. 2026-08-18 09:58 UTCGHSA enrichment
  57. 2026-08-17 21:19 UTCEG score recompute
  58. 2026-08-17 21:19 UTCVendor advisory
  59. 2026-08-17 21:19 UTCGHSA enrichment
  60. 2026-08-17 13:47 UTCEPSS rescore
  61. 2026-08-17 05:24 UTCVendor advisory
  62. 2026-08-17 05:24 UTCGHSA enrichment
  63. 2026-08-17 02:05 UTCEG score recompute
  64. 2026-08-17 02:05 UTCVendor advisory
  65. 2026-08-17 02:05 UTCGHSA enrichment
  66. 2026-08-16 14:56 UTCEPSS rescore
  67. 2026-08-16 13:31 UTCEG score recompute
  68. 2026-08-16 13:31 UTCVendor advisory
  69. 2026-08-16 13:31 UTCGHSA enrichment
  70. 2026-08-16 02:14 UTCEPSS rescore
  71. 2026-08-16 00:57 UTCVendor advisory
  72. 2026-08-16 00:57 UTCGHSA enrichment
  73. 2026-08-15 12:23 UTCEG score recompute
  74. 2026-08-15 12:23 UTCVendor advisory
  75. 2026-08-15 12:23 UTCGHSA enrichment

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 August 17, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 93.3% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.