CVE-2026-53235

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
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.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

net: add pskb_may_pull() to skb_gro_receive_list()

skb_gro_receive_list() calls skb_pull(skb, skb_gro_offset(skb)) without first ensuring the data is in the linear area via pskb_may_pull(). When the skb arrives via napi_gro_frags(), skb_headlen can be 0 (all data in page fragments) while skb_gro_offset is non-zero (after IP+TCP header parsing). The skb_pull() then decrements skb->len by skb_gro_offset but skb->data_len stays unchanged, hitting BUG_ON(skb->len < skb->data_len) in __skb_pull().

The UDP fraglist GRO path already contains this guard at udp_offload.c:749. Adding it to skb_gro_receive_list() itself provides centralized protection for all callers (TCP, UDP, and any future protocols), and ensures the precondition of skb_pull() is satisfied before it is called.

On pskb_may_pull() failure, set NAPI_GRO_CB(skb)->flush = 1 so the skb is not held as a new GRO head and is instead delivered through the normal receive path, matching the UDP handling.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

net: add pskb_may_pull() to skb_gro_receive_list() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: add pskb_may_pull() to skb_gro_receive_list() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e636c995b7beeb74ea882968248752821c244c4
generic

net: add pskb_may_pull() to skb_gro_receive_list() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/848571dcbbbea7ba44dd4f7ebe1fbb274afe08ac
generic

net: add pskb_may_pull() to skb_gro_receive_list() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cde3a004119db637b401c54e77536e4145fc0b4

Vendor Advisories for CVE-2026-53235(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Data Freshness Timeline

(refreshed 5× in last 7d / 60× 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 205 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53235?
CVE-2026-53235 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: add pskbmaypull() to skbgroreceive_list() skbgroreceivelist() calls skbpull(skb, skbgrooffset(skb)) without first ensuring the data is in the linear area via pskbmaypull(). When the skb arrives via napigrofrags(), skb_headlen…
When was CVE-2026-53235 disclosed?
CVE-2026-53235 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53235 actively exploited?
CVE-2026-53235 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 62.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53235?
CVE-2026-53235 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53235?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53235, 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-53235

Explore →

Is Your Infrastructure Affected by CVE-2026-53235?

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

Start Free Scan →Browse All CVEs