CVE-2026-98289: af_unix: Unify scc_index when finalising SCC in __unix_walk_scc().

Published Oct 6, 2026

Updated

afunix: Unify sccindex when finalising SCC in unixwalkscc().

Affected Software

1 affected component

Linux Linux kernel

Event History

Oct 6, 2026

CVE Published

via MITRE·08:45 AM

Data Sourced

via MITRE·08:45 AM

Description

Data Sourced

via NVD·09:18 AM

Description

Oct 7, 2026

Data Sourced

via Microsoft·08:40 AM

DescriptionSeverityWeakness

Frequently Asked Questions

What condition triggers the failure?

It requires an AF_UNIX socket graph containing a strongly connected component with two or more back edges. Whether the problem occurs also depends on the depth-first-search traversal order; the same graph may not trigger it when walked in a different order or from a different starting vertex.

What is the practical effect when the condition occurs?

unix_vertex_dead() can treat a vertex as belonging to a different strongly connected component because vertices in the same component have inconsistent scc_index values. As a result, the affected component is not garbage-collected.

How can I determine whether a kernel includes a fix?

Check the kernel source or vendor patch history for one of the referenced stable fixes: b8f71d69380a5fbc734c868acbeb560f1de1766f, be550ee108ad80828aa61280400bedfc7e7c39d3, or 4a4263dfeabad72f95e8ab6e15146861fa4144dd. The supplied information does not identify affected or fixed kernel version numbers.

CVE-2026-98289: af_unix: Unify scc_index when finalising SCC in __unix_walk_scc().

Affected Software

Event History

Frequently Asked Questions

What condition triggers the failure?

What is the practical effect when the condition occurs?

How can I determine whether a kernel includes a fix?

Company

Resources

Contact

Frequently Asked Questions

What condition triggers the failure?

What is the practical effect when the condition occurs?

How can I determine whether a kernel includes a fix?