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.8% 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-80630 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80630?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80630?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-80630 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 | from 5.10.241 before 5.10.261 |
| Linux | from 5.15.190 before 5.15.212 |
| Linux | from 6.1.135 before 6.1.178 |
| Linux | from 6.6.88 before 6.6.145 |
| Linux | from 6.12.24 before 6.12.97 |
| Linux | from 5.4.297 before 5.5 |
| Linux | from 6.13.12 before 6.14 |
| Linux | from 6.14.3 before 6.15 |
| Linux | 6.15 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 5.10 | 5.10.261 |
| Linux | 5.15 | 5.15.212 |
| Linux | 6.1 | 6.1.178 |
| Linux | 6.6 | 6.6.145 |
| Linux | 6.12 | 6.12.97 |
| Linux | 6.18 | 6.18.40 |
| Linux | 7.1 | 7.1.5 |
| Linux | later releases | 7.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.180-1 | DEBIAN-CVE-2026-80630 |
| Debian | 13 | linux | 6.12.100-1 | DEBIAN-CVE-2026-80630 |
| Debian | 14 | linux | 7.1.5-1 | DEBIAN-CVE-2026-80630 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-80630 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-80630 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-80630 |
| Ubuntu | 22.04:LTS | linux | 5.15.0-198.208 | UBUNTU-CVE-2026-80630 USN-8875-1 |
| Ubuntu | 22.04:LTS | linux-aws | 5.15.0-1117.124 | UBUNTU-CVE-2026-80630 USN-8875-1 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-80630 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure | 5.15.0-1123.132 | UBUNTU-CVE-2026-80630 USN-8875-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-80630 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde | 5.15.0-1122.131 | UBUNTU-CVE-2026-80630 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-80630 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp | 5.15.0-1118.128 | UBUNTU-CVE-2026-80630 USN-8877-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-80630 USN-9024-1 |
| 80 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Alpaquita | 23 | linux-lts | 6.1.182-r0 | BELL-CVE-2026-80630 |
| Alpaquita | 25 | linux-lts | 6.12.103-r0 | BELL-CVE-2026-80630 |
| Alpaquita | stream | linux-lts | 6.18.43-r0 | BELL-CVE-2026-80630 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.
Red Hat rates this Moderate.
fq_codel could call qdisc_tree_reduce_backlog during peek before restoring qlen after putting the skb back on gso_skb. If qlen temporarily reaches zero, the parent qdisc can run qlen_notify and incorrectly deactivate a class even though fq_codel still has a packet queued. In a qfq parent setup this can corrupt scheduler state and was observed as a KASAN wild memory access in qfq_deactivate_agg followed by a kernel oops. For the CVSS the PR:L is used for the paranoid score because an untrusted local user may be able to control qdisc state through a network namespace, container, or delegated CAP_NET_ADMIN rather than full host root. The issue is not directly network reachable and is triggered through local traffic control operations, but packet enqueue or peek behavior can be part of the trigger once the qdisc hierarchy is configured. Impact is at least local denial of service via kernel crash and in worst case may allow confidentiality or integrity impact due to memory corruption like behavior, so it should be reviewed manually.
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 7 | kernel-rt | Fix deferred | |
| Red Hat Enterprise Linux 8 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 8 | kernel-rt | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Fix deferred |
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-80630.