CVE-2026-80521: af_unix: Unlink scc_entry in unix_del_edge().
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().
- BDU:2026-15216
- EUVD-2026-66587
- ALSA-2026:81406
- RHSA-2026:77634
- RHSA-2026:81406
- RLSA-2026:81406
- SUSE-SU-2026:24521-1
- SUSE-SU-2026:24522-1
- SUSE-SU-2026:24523-1
- SUSE-SU-2026:24524-1
- SUSE-SU-2026:24525-1
- SUSE-SU-2026:24526-1
- SUSE-SU-2026:24527-1
- SUSE-SU-2026:24528-1
- SUSE-SU-2026:24529-1
- SUSE-SU-2026:24530-1
- SUSE-SU-2026:24531-1
- SUSE-SU-2026:24532-1
- SUSE-SU-2026:24533-1
- SUSE-SU-2026:24534-1
- Published
- Aug 26, 2026
- Updated
- Oct 3, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.65.1.el10_2 | 6.12.0-211.65.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- 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 leaders31Monitor
- ← EarlierCVE-2026-74754Aug 26, 2026 · scsi: core: pair EH runtime PM get and put0Monitor
- 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 / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1293fd69a50d188a5788b08ba3741a3e86be1608 | Vendor (CNA) |
| Linux Linux | 2b6c2842692d08e7acaf32d1eb47f95def35f3fe | Vendor (CNA) |
| Linux Linux | 594d905195024b228c962627ae5ae7c17bd582a4 | Vendor (CNA) |
| Linux Linux | 6.1.189 | Vendor (CNA) |
| Linux Linux | 6.6.158 | Vendor (CNA) |
| Linux Linux | 6fda5c51b8e43a8440f76e65c89d9f95ddb2ef33 | Vendor (CNA) |
| Linux Linux | e3702470ced94fad74d71e2232f022d2eb752a6d | Vendor (CNA) |
| Linux Linux | fe198b077864feafd4aa4b33b1a5ce26f50195a2 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.65.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-55.109.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-55.109.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-55.109.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-55.109.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-55.109.1.el10_0 · Red Hat:enterprise_linux_eus:10.0 | Package 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.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:49 | 2026-09-16 |
| Proof-of-concept repository on GitHub | stars:1 | 2026-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.
- Published
- First PoC+20 d
- TodayNov 16, 2026+82 d
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.
- TR-26-0919 · Aug 27, 2026(Linux Kernel Güvenlik Bildirimi)
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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2b6c2842692d08e7acaf32d1eb47f95def35f3fe
- git.kernel.org/stable/c/594d905195024b228c962627ae5ae7c17bd582a4
- git.kernel.org/stable/c/6fda5c51b8e43a8440f76e65c89d9f95ddb2ef33
- git.kernel.org/stable/c/e3702470ced94fad74d71e2232f022d2eb752a6d
- git.kernel.org/stable/c/fe198b077864feafd4aa4b33b1a5ce26f50195a2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.