Linux
af_unix: Unlink scc_entry in unix_del_edge().
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().
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 5dfd283f4651d04dbb70ceb9ae5c4a30eda3c52a, < 2b6c2842692d08e7acaf32d1eb47f95def35f3fe
- >= de7921631ff323369aa63a4324695ab54ea4047e, < 6fda5c51b8e43a8440f76e65c89d9f95ddb2ef33
- >= 4090fa373f0e763c43610853d2774b5979915959, < 1293fd69a50d188a5788b08ba3741a3e86be1608
- >= 4090fa373f0e763c43610853d2774b5979915959, < fe198b077864feafd4aa4b33b1a5ce26f50195a2
- >= 4090fa373f0e763c43610853d2774b5979915959, < e3702470ced94fad74d71e2232f022d2eb752a6d
- >= 4090fa373f0e763c43610853d2774b5979915959, < 594d905195024b228c962627ae5ae7c17bd582a4
- >= 6.1.141, < 6.1.189
- >= 6.6.93, < 6.6.158
Fixed in 2b6c2842692d08e7acaf32d1eb47f95def35f3fe, 6fda5c51b8e43a8440f76e65c89d9f95ddb2ef33, 1293fd69a50d188a5788b08ba3741a3e86be1608, fe198b077864feafd4aa4b33b1a5ce26f50195a2, e3702470ced94fad74d71e2232f022d2eb752a6d, 594d905195024b228c962627ae5ae7c17bd582a4, 6.1.189, 6.6.158
- 6.10
Fixed in 0, 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.1.10, 7.2
Mitigation
Upgrade Linux to 2b6c2842692d08e7acaf32d1eb47f95def35f3fe or 6fda5c51b8e43a8440f76e65c89d9f95ddb2ef33 or 1293fd69a50d188a5788b08ba3741a3e86be1608 or fe198b077864feafd4aa4b33b1a5ce26f50195a2 or e3702470ced94fad74d71e2232f022d2eb752a6d or 594d905195024b228c962627ae5ae7c17bd582a4 or 6.1.189 or 6.6.158 or later.
Upgrade Linux to 0 or 6.1.189 or 6.6.158 or 6.12.111 or 6.18.53 or 7.1.10 or 7.2 or later.
Timeline
Days relative to CVE publicationFirst public PoC 21 days after publication; not in CISA KEV. First PoC: Markakd/Container_escape (created 16 Sep 2026, found by us: backfilled).
PoC repositories
Found on GitHub.2 PoCs
PoCs 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Markakd/Container_escape | 16 Sep 2026 +21 d | 49 | PoC |
| rifkyards/Container_escape-CVE-2026-80521-CVE-2026-52910 | 29 Sep 2026 +34 d | 1 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.