CVE-2026-53235

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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(high)
EPSS
37.1%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 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(1)

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

Data Freshness Timeline

(refreshed 32× in last 7d / 44× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:06 UTCEG score recompute
  4. 2026-07-06 16:06 UTCGHSA enrichment
  5. 2026-07-06 02:58 UTCEG score recompute
  6. 2026-07-06 02:58 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 13:52 UTCEG score recompute
  10. 2026-07-05 13:51 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-05 00:45 UTCEG score recompute
  14. 2026-07-05 00:45 UTCGHSA enrichment
  15. 2026-07-04 11:40 UTCEG score recompute
  16. 2026-07-04 11:40 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 22:34 UTCEG score recompute
  20. 2026-07-03 22:34 UTCGHSA enrichment
  21. 2026-07-03 09:24 UTCEG score recompute
  22. 2026-07-03 09:24 UTCGHSA enrichment
  23. 2026-07-02 20:18 UTCEG score recompute
  24. 2026-07-02 20:18 UTCGHSA enrichment
  25. 2026-07-02 07:12 UTCEG score recompute
Show 19 more
  1. 2026-07-02 07:12 UTCGHSA enrichment
  2. 2026-07-01 18:04 UTCEG score recompute
  3. 2026-07-01 18:04 UTCGHSA enrichment
  4. 2026-07-01 15:07 UTCEPSS rescore
  5. 2026-07-01 04:59 UTCEG score recompute▲ 7.50
  6. 2026-07-01 04:59 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-29 14:06 UTCEPSS rescore
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-28 14:07 UTCEPSS rescore
  11. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  12. 2026-06-28 07:32 UTCEG score recompute
  13. 2026-06-28 07:32 UTCGHSA enrichment
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-25 10:06 UTCEG score recompute
  19. 2026-06-25 10:06 UTCGHSA enrichment

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 June 30, 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 37.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53235?
CVE-2026-53235 has a CVSS v3 base score of 7.5 (NVD).
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

Explore the affected products and dependency analysis for 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