BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-53235High confidence

net: add pskb_may_pull() to skb_gro_receive_list()

Linux · Linux

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.44% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

17 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 13 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fde-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidia-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracle-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-53235 · CSAF 2.0 · revision 10 · interimSUSE Product Security TeamCVE-2026-53235
2 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
Summary
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 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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-53235 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: net: add pskb_may_pull() to skb_gro_receive_list()
309 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • kernel-64k-debug-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-debug-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-debug-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-64k-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • kernel-debug-devel-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
Summary
A flaw was found in the Linux kernel's network Generic Receive Offload (GRO) handling. An attacker sending specially crafted network packets could trigger a bug in the `skb_gro_receive_list()` function. This occurs when the system attempts to process network data that is not in the expected linear memory area, leading to an incorrect buffer length calculation. The flaw can cause a system crash, resulting in a Denial of Service (DoS).
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-39326

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2077Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53226 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=CVE-2026-53227 Référence CVE CVE-2026-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53229 https://www.cve.org/CVERecord?id=CVE-2026-53229 Référence CVE CVE-2026-53230 https://www.cve.org/CVERecord?id=CVE-2026-53230 Référence CVE CVE-2026-53231 https://www.cve.org/CVERecord?id=CVE-2026-53231 Référence CVE CVE-2026-53232 https://www.cve.org/CVERecord?id=CVE-2026-53232 Référence CVE CVE-2026-53233 https://www.cve.org/CVERecord?id=CVE-2026-53233 Référence CVE CVE-2026-53234 https://www.cve.org/CVERecord?id=CVE-2026-53234 Référence CVE CVE-2026-53235 https://www.cve.org/CVERecord?id=CVE-2026-53235 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=CVE-2026-53236 Référence CVE CVE-2026-53237 https://www.cve.org/CVERecord?id=CVE-2026-53237 Référence CVE CVE-2026-53238 https://www.cve.org/CVERecord?id=CVE-2026-53238 Référence CVE CVE-2026-53239 https://www.cve.org/CVERecord?id=CVE-2026-53239 Référence CVE CVE-2026-53240 https://www.cve.org/CVERecord?id=CVE-2026-53240 Référence CVE CVE-2026-53241 https://www.cve.org/CVERecord?id=CVE-2026-53241 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53244 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53226 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=CVE-2026-53227 Référence CVE CVE-2026-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53229 https://www.cve.org/CVERecord?id=CVE-2026-53229 Référence CVE CVE-2026-53230 https://www.cve.org/CVERecord?id=CVE-2026-53230 Référence CVE CVE-2026-53231 https://www.cve.org/CVERecord?id=CVE-2026-53231 Référence CVE CVE-2026-53232 https://www.cve.org/CVERecord?id=CVE-2026-53232 Référence CVE CVE-2026-53233 https://www.cve.org/CVERecord?id=CVE-2026-53233 Référence CVE CVE-2026-53234 https://www.cve.org/CVERecord?id=CVE-2026-53234 Référence CVE CVE-2026-53235 https://www.cve.org/CVERecord?id=CVE-2026-53235 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=CVE-2026-53236 Référence CVE CVE-2026-53237 https://www.cve.org/CVERecord?id=CVE-2026-53237 Référence CVE CVE-2026-53238 https://www.cve.org/CVERecord?id=CVE-2026-53238 Référence CVE CVE-2026-53239 https://www.cve.org/CVERecord?id=CVE-2026-53239 Référence CVE CVE-2026-53240 https://www.cve.org/CVERecord?id=CVE-2026-53240 Référence CVE CVE-2026-53241 https://www.cve.org/CVERecord?id=CVE-2026-53241 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53243 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53226 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=CVE-2026-53227 Référence CVE CVE-2026-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53229 https://www.cve.org/CVERecord?id=CVE-2026-53229 Référence CVE CVE-2026-53230 https://www.cve.org/CVERecord?id=CVE-2026-53230 Référence CVE CVE-2026-53231 https://www.cve.org/CVERecord?id=CVE-2026-53231 Référence CVE CVE-2026-53232 https://www.cve.org/CVERecord?id=CVE-2026-53232 Référence CVE CVE-2026-53233 https://www.cve.org/CVERecord?id=CVE-2026-53233 Référence CVE CVE-2026-53234 https://www.cve.org/CVERecord?id=CVE-2026-53234 Référence CVE CVE-2026-53235 https://www.cve.org/CVERecord?id=CVE-2026-53235 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=CVE-2026-53236 Référence CVE CVE-2026-53237 https://www.cve.org/CVERecord?id=CVE-2026-53237 Référence CVE CVE-2026-53238 https://www.cve.org/CVERecord?id=CVE-2026-53238 Référence CVE CVE-2026-53239 https://www.cve.org/CVERecord?id=CVE-2026-53239 Référence CVE CVE-2026-53240 https://www.cve.org/CVERecord?id=CVE-2026-53240 Référence CVE CVE-2026-53241 https://www.cve.org/CVERecord?id=CVE-2026-53241 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53243 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53226 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=CVE-2026-53227 Référence CVE CVE-2026-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53229 https://www.cve.org/CVERecord?id=CVE-2026-53229 Référence CVE CVE-2026-53230 https://www.cve.org/CVERecord?id=CVE-2026-53230 Référence CVE CVE-2026-53231 https://www.cve.org/CVERecord?id=CVE-2026-53231 Référence CVE CVE-2026-53232 https://www.cve.org/CVERecord?id=CVE-2026-53232 Référence CVE CVE-2026-53233 https://www.cve.org/CVERecord?id=CVE-2026-53233 Référence CVE CVE-2026-53234 https://www.cve.org/CVERecord?id=CVE-2026-53234 Référence CVE CVE-2026-53235 https://www.cve.org/CVERecord?id=CVE-2026-53235 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=CVE-2026-53236 Référence CVE CVE-2026-53237 https://www.cve.org/CVERecord?id=CVE-2026-53237 Référence CVE CVE-2026-53238 https://www.cve.org/CVERecord?id=CVE-2026-53238 Référence CVE CVE-2026-53239 https://www.cve.org/CVERecord?id=CVE-2026-53239 Référence CVE CVE-2026-53240 https://www.cve.org/CVERecord?id=CVE-2026-53240 Référence CVE CVE-2026-53241 https://www.cve.org/CVERecord?id=CVE-2026-53241 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53243 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53214 Référence CVE CVE-2026-53218 https://www.cve.org/CVERecord?id=CVE-2026-53218 Référence CVE CVE-2026-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53225 https://www.cve.org/CVERecord?id=CVE-2026-53225 Référence CVE CVE-2026-53226 https://www.cve.org/CVERecord?id=CVE-2026-53226 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=CVE-2026-53227 Référence CVE CVE-2026-53230 https://www.cve.org/CVERecord?id=CVE-2026-53230 Référence CVE CVE-2026-53233 https://www.cve.org/CVERecord?id=CVE-2026-53233 Référence CVE CVE-2026-53235 https://www.cve.org/CVERecord?id=CVE-2026-53235 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=CVE-2026-53236 Référence CVE CVE-2026-53237 https://www.cve.org/CVERecord?id=CVE-2026-53237 Référence CVE CVE-2026-53239 https://www.cve.org/CVERecord?id=CVE-2026-53239 Référence CVE CVE-2026-53241 https://www.cve.org/CVERecord?id=CVE-2026-53241 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53245 https://www.cve.org/CVERecord?id=CVE-2026-53245 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53247 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-023058LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。net: skb_gro_receive_list() に pskb_may_pull() を追加しました。skb_gro_receive_list() は pskb_may_pull() によりデータが線形領域に存在することを事前に確認せずに、skb_pull(skb, skb_gro_offset(skb)) を呼び出していました。napi_gro_frags() 経由で skb が到着した場合、skb_headlen は 0（すべてのデータがページフラグメント内）である一方、skb_gro_offset はゼロでない（IP+TCP ヘッダー解析後）可能性があります。すると、skb_pull() は skb-＞len を skb_gro_offset 分だけ減算しますが、skb-＞data_len は変わらず、__skb_pull() 内の BUG_ON(skb-＞len ＜ skb-＞data_len) を引き起こします。UDP の fraglist GRO パスでは既に udp_offload.c の 749 行目にこのガードが存在します。これを skb_gro_receive_list() 自体に追加することで、全ての呼び出し元（TCP、UDPおよび将来のプロトコル）に対して集中管理された保護を提供し、skb_pull() が呼び出される前に前提条件が満たされていることを保証します。pskb_may_pull() が失敗した場合には、NAPI_GRO_CB(skb)-＞flush = 1 を設定し、skb が新たな GRO ヘッドとして保持されることなく通常の受信パスを通じて配信されるようにし、UDP の処理と整合させています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.10, 6.12.94 ≤ 6.12.*, 6.18.36 ≤ 6.18.*, 7.0.13 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 25 Jun 2026 · Last source change 5 Aug 2026, 12:34 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-39326
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-39326↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-53235 · cve.blacktree.nl