CVE-2026-53235
Last modified
CVE-2026-53235 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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). EPSS estimates a 0.47% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.10, < 6.12.94 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53235?
How severe is CVE-2026-53235?
How do I fix CVE-2026-53235?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-5323A vulnerability was found in priyankark a11y-mcp up to 1.0.5…5.3
- CVE-2026-53230In the Linux kernel, the following vulnerability has been re…8.7
- CVE-2026-53231In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53232In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53233In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53234In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53236In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53237In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53238In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53239In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5324The Brizy – Page Builder plugin for WordPress is vulnerable …7.2
- CVE-2026-53240In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2026-53235?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
