Skip to content
Reachability Analysis

CVE-2026-80521: Linux kernel, is it exploitable where you run it

Code called: yesReached: openControl in front: noExploitation known: noWalk it through the four questions

What the flaw is

The kernel passes open sockets between processes over UNIX domain sockets. A garbage collector frees groups of such sockets that nothing can reach any more. Since Linux 6.10 it tracks the groups as strongly connected components.

Kyle Zeng reported that a socket sent to itself while its group is being closed can leave the collector in a half-finished state. One group is judged dead but not freed, because a message that holds a reference is not yet queued. The next collection run then walks to a freed entry through its scc_entry list link. The result is a use-after-free in the kernel.

Red Hat rates the flaw Important and says an authenticated local user can use the race to corrupt kernel memory, with a possible local privilege escalation. The fix adds one line that unlinks scc_entry in unix_del_edge() before the entry is freed. CISA's KEV catalog and the vendor trackers list no exploitation of this flaw.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
the running kernel has the new UNIX socket garbage collector and lacks the fixRun uname -r and compare with the versions table. The collector is in mainline 6.10 or later, in 6.6.93 or later and 6.1.141 or later in those lines, and in Ubuntu's 6.8 kernels. A distribution kernel can carry the fix under an older version number, so on RPM systems run rpm -q --changelog kernel | grep CVE-2026-80521, and on Debian and Ubuntu run apt changelog linux-image-$(uname -r) | grep CVE-2026-80521, or use the Debian and Ubuntu trackers.
an attacker already runs code on the host as an unprivileged local userUnprivileged users can create UNIX domain sockets by default (CVSS AV:L, PR:L). List who can log in or execute code: getent passwd, last, service accounts, CI runners and container workloads. Without a local foothold this CVE is not reachable.

Affected and fixed versions

NVD has not analyzed this record and lists no version ranges. The ranges above come from the kernel.org change logs and the vendor trackers. The 6.1.141 and 6.6.93 change logs (4 Jun 2025) both list "af_unix: Replace garbage collection algorithm", which is why those releases are the start of the affected range in their lines. Ubuntu 6.8 kernels are affected although 6.8 is below the mainline start of 6.10: the Ubuntu noble changelog for 6.8.0-98.98 lists the backport of the af_unix garbage collection rewrite, and 6.8.0-149.149 lists this fix. Ubuntu's upstream line says the fix is in 7.2 and 7.0.y, but the kernel.org change logs for 7.0.1 through 7.0.14, the last 7.0 release, do not contain it; Ubuntu's 7.0.0-42.42 kernel carries the fix as its own backport.
Product or lineAffectedFirst fixed
Linux mainline6.10 up to and including 7.1 (rewrite landed in 6.10, 14 Jul 2024; 7.1 stable is fixed from 7.1.10, see below)7.2 (16 Aug 2026), commit 594d905195024b228c962627ae5ae7c17bd582a4
Linux 7.1 stableAll earlier 7.1.x7.1.10 (23 Aug 2026)
Linux 6.18 stableAll earlier 6.18.x6.18.53 (21 Sep 2026)
Linux 6.12 stableAll earlier 6.12.x6.12.111 (21 Sep 2026)
Linux 6.6 stable6.6.93 and later before the fix6.6.158 (3 Oct 2026)
Linux 6.1 stable6.1.141 and later before the fix6.1.189 (3 Oct 2026)
Linux 6.19 and 7.0 stable6.19.x and 7.0.x (both branches ended at 6.19.14 and 7.0.14)No kernel.org fixed release. Ubuntu fixed its own 7.0 kernel (resolute 7.0.0-42.42)
Linux 5.15 stableNot affected (no new garbage collector)Not applicable
RHEL 10All earlier kernels10.2: kernel-6.12.0-211.65.1.el10_2 (RHSA-2026:81406, 12 Oct 2026). 10.3: kernel-6.12.0-264.14.1.el10_3 (RHSA-2026:98608, 11 Nov 2026). 10.0 EUS: kernel-6.12.0-55.109.1.el10_0 (RHSA-2026:77634, 8 Oct 2026)
RHEL 6, 7, 8 and 9Not affected (Red Hat)Not applicable
Debianbookworm, trixie and unstable before the fixbookworm 6.1.190-1 (DLA-4841-1, upstream 6.1.190 includes the 6.1.189 fix), linux-6.12 on bookworm 6.12.111-1~deb12u1 (DLA-4817-1), trixie 6.12.111-1 (DSA-6528-1), unstable 7.1.10-1. Bullseye is not affected
Ubuntunoble 6.8 (Ubuntu backported the garbage collector rewrite in 6.8.0-98.98), resolute 7.0 and jammy HWE 6.8 before the fixnoble 6.8.0-149.149, jammy HWE 6.8.0-149.149~22.04.1, resolute 7.0.0-42.42. Focal, bionic, xenial and jammy 5.15 are not affected

If the fix cannot go in yet

  • Install a kernel with the fix and reboot. Cost: a reboot. This is the only remedy the vendors give.
  • Red Hat states that a mitigation is either not available or does not meet its criteria for ease of use, reach and stability. Neither Red Hat nor the kernel project publishes a workaround, and CISA has issued no guidance because the flaw is not in KEV.
  • Limiting local code execution is the only exposure-reducing step: restrict shell and CI runner access, and keep untrusted workloads off the host. User-namespace limits and seccomp profiles that still allow AF_UNIX do not remove the flaw, because AF_UNIX sockets need no privilege and no namespace. A seccomp filter that denies socket(AF_UNIX, ...) would block the path, but it breaks syslog, D-Bus, systemd clients, X11 and most container runtimes, and neither Red Hat nor the kernel project recommends it.

What to look for

  • No indicators of compromise have been published by Red Hat, Debian, Ubuntu or the kernel project, and the flaw is not in the CISA KEV catalog (feed version 2026.11.18). A successful trigger would show as a kernel oops or panic in dmesg or journalctl -k that names unix_gc or the scc_entry list, and a host that reboots without a planned change.

No public report dates the start of exploitation.

Why attack-path analysis settles it

The version and distribution tables settle whether the kernel has the new collector. The open question is whether anyone can run code on the host as a local user, which an attack-path view answers from who and what can execute there. No exploitation is known, so a known-exploited feed has nothing to say yet.

Sources

  1. CVE-2026-80521: NVD record, read 19 Nov 2026
  2. CVE-2026-80521: CISA KEV feed (catalog version 2026.11.18), no entry for this CVE, read 19 Nov 2026
  3. CVE-2026-80521: vendor advisory data (Red Hat Security Data API: errata, package versions, statement), read 19 Nov 2026
  4. CVE-2026-80521: upstream fix commit (GitHub mirror of the Linux kernel); the five stable commits in the NVD references were read the same way, read 19 Nov 2026
  5. CVE-2026-80521: kernel.org stable change log 6.1.189 (also read for 6.6.158, 6.12.111, 6.18.53, 7.1.10, 7.2, 6.1.141, 6.6.93 and 6.10), read 19 Nov 2026
  6. CVE-2026-80521: Debian security tracker, read 19 Nov 2026
  7. CVE-2026-80521: Ubuntu CVE tracker data, read 19 Nov 2026
  8. CVE-2026-80521: GitHub advisory database entry GHSA-g8mr-r59r-2xmq, read 19 Nov 2026

Last reviewed 19 Nov 2026.