dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53235

HIGH · 7.5 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to 6.12.94 / 6.18.36 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.10, < 6.12.94>= 6.13, < 6.18.36>= 6.19, < 7.0.13= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.12.94 / 6.18.36 / 7.0.13 or later
Fixed in 6.12.946.18.367.0.13
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 6.12.94+ (for 6.10-6.12 branch), 6.18.36+ (for 6.13-6.19 branch), 7.0.13+ (for 6.19-7.0 branch), or 7.2+ (for 7.1 branch)

  1. 1. Check current kernel version using 'uname -r' or 'cat /proc/version'
  2. 2. Identify which version branch your current kernel belongs to (6.10-6.12, 6.13-6.19, 6.19-7.0, or 7.1)
  3. 3. For kernels >= 6.10 and < 6.12.94: upgrade to kernel version 6.12.94 or later in the 6.12 stable series
  4. 4. For kernels >= 6.13 and < 6.18.36: upgrade to kernel version 6.18.36 or later in the 6.18 stable series
  5. 5. For kernels >= 6.19 and < 7.0.13: upgrade to kernel version 7.0.13 or later in the 7.0 stable series
  6. 6. For kernel = 7.1: upgrade to kernel version 7.2 or later in the 7.x stable series
  7. 7. Use your distribution's package manager to install the updated kernel (e.g., 'apt-get update && apt-get install linux-image-<version>' for Debian/Ubuntu, or 'yum/dnf update kernel' for RHEL/Fedora)
  8. 8. Reboot the system to load the new kernel
Caveat Kernel upgrades may require matching kernel headers and modules; ensure dependent packages are compatible with the new kernel version

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53235 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data