cve.bz

CVE-2026-80725 linux linux

9.8 criticalEPSS 0.5%Fix available

Critical (9.8) in linux linux. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: net: gro: properly validate BIG TCP aggregation criteria When GRO attempts to aggregate packets beyond GRO_LEGACY_MAX_SIZE (64KB), BIG TCP should only be permitted for plain IPv4 TCP and plain IPv6 TCP (with sufficient MAC header room to insert the temporary HBH jumbo header). However, commit b1a78b9b9886 ("net: add support for ipv4 big tcp") loosened the check in skb_gro_receive(), leading to several issues: 1. skb_gro_receive() checked skb_headroom(p) instead of the actual space before the MAC header (p->mac_header). Because skb_headroom(p) includes mac_len, crafted frames (e.g. injected via AF_PACKET) can pass the check with p->mac_header < 8 bytes. When ipv6_gro_complete() inserts the temporary HBH jumbo header, the memmove() starts before skb->head, causing an out-of-bounds write and wrapping skb->mac_header. 2. It allowed non-IP protocols such as software VLAN (ETH_P_8021Q / ETH_P_8021AD) to aggregate beyond 64KB because p->protocol != ETH_P_IPV6 was true. 3. It checked p->encapsulation instead of NAPI_GRO_CB(skb)->encap_mark, allowing encapsulated flows (e.g. SIT / IPv6-in-IPv4) to aggregate beyond 64KB. Fix skb_gro_receive() to strictly enforce: - NAPI_GRO_CB(skb)->proto == IPPROTO_TCP - Not encapsulated (!NAPI_GRO_CB(skb)->encap_mark && !p->encapsulation) - Protocol must be either ETH_P_IP or ETH_P_IPV6 - If ETH_P_IPV6, p->mac_header must be at least sizeof(struct hop_jumbo_hdr) Returning -E2BIG from skb_gro_receive() ensures that packets which cannot become BIG TCP are cleanly flushed at <= 64KB and delivered intact without dropping. This issue does not exist in mainline (7.0+) because the subsystem was rewritten in commit 81be30c1f5f2 ("net/ipv6: Drop HBH for BIG TCP on RX side"), making this fix relevant only for older stable branches like 6.18.y.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.1.185
  • Linux Linux: fixed in 6.6.154
  • Linux Linux: fixed in 6.12.106
  • Linux Linux: fixed in 6.18.47
  • Linux Linux: fixed in 7.0
  • Debian, Ubuntu, SUSE, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-80725 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80725?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80725?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80725 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.19 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.185
Linux6.66.6.154
Linux6.126.12.106
Linux6.186.18.47
Linuxlater releases7.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.187-1DEBIAN-CVE-2026-80725
Debian12linux-6.126.12.107-1~deb12u1DEBIAN-CVE-2026-80725
Debian13linux6.12.107-1DEBIAN-CVE-2026-80725
Debian14linux7.0.3-1DEBIAN-CVE-2026-80725
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-80725
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-80725
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-80725
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 moreno fix listedUBUNTU-CVE-2026-80725
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 41 moreno fix listedUBUNTU-CVE-2026-80725
Ubuntu24.04:LTSlinux-nvidia-tegra6.8.0-1038.42UBUNTU-CVE-2026-80725 USN-9002-1
UbuntuNvidia-BlueField:24.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2026-80725
UbuntuPro:FIPS-updates:24.04:LTSlinux-fips, linux-aws-fips, linux-gcp-fips and 1 moreno fix listedUBUNTU-CVE-2026-80725
UbuntuPro:Realtime:22.04:LTSlinux-realtime-6.8no fix listedUBUNTU-CVE-2026-80725
UbuntuPro:Realtime:24.04:LTSlinux-realtime, linux-realtime-6.14, linux-realtime-6.17 and 1 moreno fix listedUBUNTU-CVE-2026-80725
SUSELinux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6kernel-default6.4.0-150600.23.138.1SUSE-SU-2026:4660-1
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.84.1SUSE-SU-2026:4706-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.39.1SUSE-SU-2026:24197-1
SUSELinux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_321-150600.13.3.1SUSE-SU-2026:4660-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_211-150700.1.3.1SUSE-SU-2026:4640-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_221-150700.15.3.1SUSE-SU-2026:4706-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.84.1SUSE-SU-2026:4706-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.84.1.150700.17.47.1SUSE-SU-2026:4706-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150700.53.84.1SUSE-SU-2026:4706-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure6.4.0-150700.53.84.1SUSE-SU-2026:4706-1
SUSELinux Enterprise Server 15 SP6-LTSSkernel-64kb, kernel-docs, kernel-syms and 4 more6.4.0-150600.23.138.1SUSE-SU-2026:4660-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6kernel-default-base6.4.0-150600.23.138.1.150600.12.64.1SUSE-SU-2026:4660-1
15 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 16.0kernel-default-base6.12.0-160000.39.1.160000.2.25openSUSE-SU-2026:22091-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.39.1openSUSE-SU-2026:22091-1
openSUSELeap 16.1kernel-default-base6.12.0-160100.9.1.160100.3.14openSUSE-SU-2026:22309-1
openSUSELeap 16.1kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia6.12.0-160100.6.1openSUSE-SU-2026:22313-1
openSUSELeap 16.1kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160100.9.1openSUSE-SU-2026:22309-1
Azure Linux3kernel6.6.157.1-1AZL-98223
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-80725
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-80725
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-80725

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

BIG TCP GRO aggregation can incorrectly accept IPv6 aggregates above the legacy 64 KB GRO limit without fully validating the protocol, encapsulation state, and actual space available before the MAC header. In the affected code, `skb_gro_receive()` checks `skb_headroom(p)` rather than the position of `p->mac_header`. Because `skb_headroom()` also includes the MAC header length, the check can succeed even when less than the required space is available before the MAC header.

When such an IPv6 TCP aggregate is completed, `ipv6_gro_complete()` may attempt to insert the temporary Hop-by-Hop jumbo header used by the affected BIG TCP receive implementation. If `p->mac_header` is smaller than the required jumbo-header size, the associated `memmove()` can start before `skb->head`, resulting in a kernel out-of-bounds write and corruption of skb metadata. The affected GRO logic also did not correctly reject some encapsulated traffic because it relied on `p->encapsulation` without checking the receive-side `encap_mark`.

The vulnerable path is specific to BIG TCP receive aggregation. Ordinary GRO operation within the legacy 64 KB limit does not by itself reach this condition. In practice, the receiving interface must permit GRO aggregates larger than 64 KB, such as through a `gro_max_size` value above 65536. BIG TCP is a specialized high-throughput networking optimization and is normally not enabled by default, substantially limiting practical exposure compared with ordinary GRO-enabled systems. Disabling BIG TCP or limiting GRO aggregation to 64 KB or less prevents the affected oversized-aggregation path from being reached.

Crafted frame injection through mechanisms such as `AF_PACKET` provides a reliable way to control the packet layout and trigger the vulnerable condition locally. However, on an affected system with BIG TCP receive aggregation enabled, the vulnerable code also lies on the network receive GRO path. A remote or network-adjacent sender may therefore be able to cause an IPv6 TCP flow to be aggregated beyond 64 KB without requiring a local account. For the paranoid CVSS assessment, `PR:N` reflects this network-receive exposure. Practical exploitability nevertheless depends on the BIG TCP configuration and on reaching the specific skb layout that allows the invalid jumbo-header insertion.

The confirmed primitive is a kernel out-of-bounds write rather than a NULL-pointer dereference, resource exhaustion, or simple packet-processing failure. The directly supported impact is at least denial of service through kernel memory corruption and a possible kernel crash. Because the write occurs outside the valid skb allocation boundary, corruption of adjacent kernel memory may potentially have integrity or confidentiality consequences under favorable memory-layout conditions.

Red Hat's mitigation

Disable Generic Receive Offload (GRO) on network interfaces to prevent aggregation of incoming frames beyond legacy size limits.

To disable GRO immediately on a network interface:

# ethtool -K <interface> gro off

Caveats:

Disabling GRO can reduce TCP receive throughput and increase CPU load under high network traffic. This change takes effect immediately without restarting network services, but it does not persist across system reboots unless added to interface configuration scripts.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-80725.

References

Check your stackJSON