Local socket resource leak via inconsistent SCC indices
Published Oct 6, 2026 · Updated Oct 6, 2026
Resource leak in Linux kernel AF_UNIX garbage collection allows local users to retain dead socket cycles through crafted SCM_RIGHTS graphs. In net/unix/garbage.c, __unix_walk_scc() leaves members of one strongly connected component with different scc_index values, so unix_vertex_dead() mistakes a dead cycle for a live one and skips collection. The trigger requires a local process to pass socket file descriptors into a cyclic graph; retained sockets consume resources, while the upstream report establishes no remote trigger or immediate crash.
Summary
What happened
Resource leak in Linux kernel AF_UNIX garbage collection allows local users to retain dead socket cycles through crafted SCM_RIGHTS graphs. In net/unix/garbage.c, __unix_walk_scc() leaves members of one strongly connected component with different scc_index values, so unix_vertex_dead() mistakes a dead cycle for a live one and skips collection. The trigger requires a local process to pass socket file descriptors into a cyclic graph; retained sockets consume resources, while the upstream report establishes no remote trigger or immediate crash.
The record
- CVE
- CVE-2026-98289
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4090fa373f0e763c43610853d2774b5979915959 <4a4263dfeabad72f95e8ab6e15146861fa4144dd
- Affected versionversion=4090fa373f0e763c43610853d2774b5979915959 <b8f71d69380a5fbc734c868acbeb560f1de1766f
- Affected versionversion=4090fa373f0e763c43610853d2774b5979915959 <be550ee108ad80828aa61280400bedfc7e7c39d3
- Affected versionversion=5dfd283f4651d04dbb70ceb9ae5c4a30eda3c52a
- Affected versionversion=6.10
- Affected versionversion=6.1.141 <6.2
- Affected versionversion=6.6.93 <6.7
- Affected versionversion=de7921631ff323369aa63a4324695ab54ea4047e
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- AF_UNIX mixed-lowpoint regression testproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started