Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-80521, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 5dfd283f4651d04dbb70ceb9ae5c4a30eda3c52a – < 2b6c2842692d08e7acaf32d1eb47f95def35f3fe
    • affected de7921631ff323369aa63a4324695ab54ea4047e – < 6fda5c51b8e43a8440f76e65c89d9f95ddb2ef33
    • affected 4090fa373f0e763c43610853d2774b5979915959 – < 1293fd69a50d188a5788b08ba3741a3e86be1608
    • affected 4090fa373f0e763c43610853d2774b5979915959 – < fe198b077864feafd4aa4b33b1a5ce26f50195a2
    • affected 4090fa373f0e763c43610853d2774b5979915959 – < e3702470ced94fad74d71e2232f022d2eb752a6d
    • affected 4090fa373f0e763c43610853d2774b5979915959 – < 594d905195024b228c962627ae5ae7c17bd582a4
    • affected 6.1.141 – < 6.1.189
    • affected 6.6.93 – < 6.6.158
  • Linux · Linux

    • affected 6.10
    • unaffected < 6.10
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.1.10 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80521 badge
[![CVE-2026-80521](https://cveledger.app/badge/CVE-2026-80521.svg)](https://cveledger.app/cve/CVE-2026-80521)

Record last updated .