CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8) in linux linux. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 5.19 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.1 | 6.1.185 |
| Linux | 6.6 | 6.6.154 |
| Linux | 6.12 | 6.12.106 |
| Linux | 6.18 | 6.18.47 |
| Linux | later releases | 7.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.187-1 | DEBIAN-CVE-2026-80725 |
| Debian | 12 | linux-6.12 | 6.12.107-1~deb12u1 | DEBIAN-CVE-2026-80725 |
| Debian | 13 | linux | 6.12.107-1 | DEBIAN-CVE-2026-80725 |
| Debian | 14 | linux | 7.0.3-1 | DEBIAN-CVE-2026-80725 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-80725 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-80725 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-80725 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 more | no fix listed | UBUNTU-CVE-2026-80725 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 41 more | no fix listed | UBUNTU-CVE-2026-80725 |
| Ubuntu | 24.04:LTS | linux-nvidia-tegra | 6.8.0-1038.42 | UBUNTU-CVE-2026-80725 USN-9002-1 |
| Ubuntu | Nvidia-BlueField:24.04:LTS | linux-bluefield | no fix listed | UBUNTU-CVE-2026-80725 |
| Ubuntu | Pro:FIPS-updates:24.04:LTS | linux-fips, linux-aws-fips, linux-gcp-fips and 1 more | no fix listed | UBUNTU-CVE-2026-80725 |
| Ubuntu | Pro:Realtime:22.04:LTS | linux-realtime-6.8 | no fix listed | UBUNTU-CVE-2026-80725 |
| Ubuntu | Pro:Realtime:24.04:LTS | linux-realtime, linux-realtime-6.14, linux-realtime-6.17 and 1 more | no fix listed | UBUNTU-CVE-2026-80725 |
| SUSE | Linux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6 | kernel-default | 6.4.0-150600.23.138.1 | SUSE-SU-2026:4660-1 |
| SUSE | Linux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 more | kernel-default | 6.4.0-150700.53.84.1 | SUSE-SU-2026:4706-1 |
| SUSE | Linux Enterprise High Availability Extension 16.0 | kernel-default | 6.12.0-160000.39.1 | SUSE-SU-2026:24197-1 |
| SUSE | Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_32 | 1-150600.13.3.1 | SUSE-SU-2026:4660-1 |
| SUSE | Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_21 | 1-150700.1.3.1 | SUSE-SU-2026:4640-1 |
| SUSE | Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_22 | 1-150700.15.3.1 | SUSE-SU-2026:4706-1 |
| SUSE | Linux Enterprise Module for Basesystem 15 SP7 | kernel-64kb, kernel-source, kernel-default and 1 more | 6.4.0-150700.53.84.1 | SUSE-SU-2026:4706-1 |
| SUSE | Linux Enterprise Module for Basesystem 15 SP7 | kernel-default-base | 6.4.0-150700.53.84.1.150700.17.47.1 | SUSE-SU-2026:4706-1 |
| SUSE | Linux Enterprise Module for Development Tools 15 SP7 | kernel-docs, kernel-syms, kernel-source and 1 more | 6.4.0-150700.53.84.1 | SUSE-SU-2026:4706-1 |
| SUSE | Linux Enterprise Module for Public Cloud 15 SP7 | kernel-azure | 6.4.0-150700.53.84.1 | SUSE-SU-2026:4706-1 |
| SUSE | Linux Enterprise Server 15 SP6-LTSS | kernel-64kb, kernel-docs, kernel-syms and 4 more | 6.4.0-150600.23.138.1 | SUSE-SU-2026:4660-1 |
| SUSE | Linux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6 | kernel-default-base | 6.4.0-150600.23.138.1.150600.12.64.1 | SUSE-SU-2026:4660-1 |
| 15 more for SUSE in the JSON and on SUSE's page. | ||||
| openSUSE | Leap 16.0 | kernel-default-base | 6.12.0-160000.39.1.160000.2.25 | openSUSE-SU-2026:22091-1 |
| openSUSE | Leap 16.0 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160000.39.1 | openSUSE-SU-2026:22091-1 |
| openSUSE | Leap 16.1 | kernel-default-base | 6.12.0-160100.9.1.160100.3.14 | openSUSE-SU-2026:22309-1 |
| openSUSE | Leap 16.1 | kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia | 6.12.0-160100.6.1 | openSUSE-SU-2026:22313-1 |
| openSUSE | Leap 16.1 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160100.9.1 | openSUSE-SU-2026:22309-1 |
| Azure Linux | 3 | kernel | 6.6.157.1-1 | AZL-98223 |
| Alpaquita | 23 | linux-lts | 6.1.189-r0 | BELL-CVE-2026-80725 |
| Alpaquita | 25 | linux-lts | 6.12.111-r0 | BELL-CVE-2026-80725 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-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 rates this Important.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Affected | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Affected |
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.