Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80521: af_unix: Unlink scc_entry in unix_del_edge().

HighCVSS 7.8 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1293fd69a50d188a5788b08ba3741a3e86be1608, 2b6c2842692d08e7acaf32d1eb47f95def35f3fe, 594d905195024b228c962627ae5ae7c17bd582a4; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1293fd69a50d188a5788b08ba3741a3e86be1608, 2b6c2842692d08e7acaf32d1eb47f95def35f3fe, 594d905195024b228c962627ae5ae7c17bd582a4; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: af_unix: Unlink scc_entry in unix_del_edge(). Kyle Zeng reported that GC could free a dead SCC partially. The scenario is as follows: 1) Create two SCCs: X -. A <-> B ^--' 2) Run the following concurrently: 2-1) send() sk-B to sk-B from sk-X 2-2) close() both A and B At 2-1), there is a small window where unix_add_edges() publishes a new edge (B <-> B) to GC but its skb is not queued by skb_queue_tail(). If 2-2) completes before skb_queue_tail() and GC is triggered, it judges A <-> B as dead, but B is not freed because GC cannot collect the not-yet-queued skb holding the B <-> B edge. X -. A <-> B -. This edge is visible ^--' ^..' but skb is not This itself is not a problem since the next GC run will judge B as dead as well and free it finally. X -. A <.> B -. ^--' ^--' However, X's SCC forces the next GC to call unix_walk_scc_fast(), and it iterates over A through B's scc_entry. Let's unlink scc_entry before freeing the vertex in unix_del_edge().

Published
Aug 26, 2026
Updated
Oct 3, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80521

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.10affected
    • 5dfd283f4651d04dbb70ceb9ae5c4a30eda3c52a and later · before 2b6c2842692d08e7acaf32d1eb47f95def35f3feaffected · git
    • de7921631ff323369aa63a4324695ab54ea4047e and later · before 6fda5c51b8e43a8440f76e65c89d9f95ddb2ef33affected · git
    • 4090fa373f0e763c43610853d2774b5979915959 and later · before 1293fd69a50d188a5788b08ba3741a3e86be1608affected · git
    • 4090fa373f0e763c43610853d2774b5979915959 and later · before fe198b077864feafd4aa4b33b1a5ce26f50195a2affected · git
    • 4090fa373f0e763c43610853d2774b5979915959 and later · before e3702470ced94fad74d71e2232f022d2eb752a6daffected · git
    • 4090fa373f0e763c43610853d2774b5979915959 and later · before 594d905195024b228c962627ae5ae7c17bd582a4affected · git
    • 6.1.141 and later · before 6.1.189affected · semver
    • 6.6.93 and later · before 6.6.158affected · semver
    • before 6.10not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74753Aug 26, 2026 · perf: Reject exited events as group leaders
    31Monitor
  • ← EarlierCVE-2026-74754Aug 26, 2026 · scsi: core: pair EH runtime PM get and put
    0Monitor
  • Later →CVE-2026-80522Aug 26, 2026 · crypto: tegra - fix rctx->cryptlen calculation in tegra_gcm_do_one_req()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1293fd69a50d188a5788b08ba3741a3e86be1608Vendor (CNA)
Linux Linux2b6c2842692d08e7acaf32d1eb47f95def35f3feVendor (CNA)
Linux Linux594d905195024b228c962627ae5ae7c17bd582a4Vendor (CNA)
Linux Linux6.1.189Vendor (CNA)
Linux Linux6.6.158Vendor (CNA)
Linux Linux6fda5c51b8e43a8440f76e65c89d9f95ddb2ef33Vendor (CNA)
Linux Linuxe3702470ced94fad74d71e2232f022d2eb752a6dVendor (CNA)
Linux Linuxfe198b077864feafd4aa4b33b1a5ce26f50195a2Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.158.1-1 · Release NotesMicrosoft (MSRC)
almalinux:kernel6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.109.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.109.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.109.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.109.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.109.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)

+20

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:492026-09-16
Proof-of-concept repository on GitHubstars:12026-09-29

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+20 d
  3. TodayNov 16, 2026+82 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records