Kernel crash via uninitialized SMB reconnect list
Published Oct 6, 2026 · Updated Oct 6, 2026
A reconnect-list flaw in the Linux SMB client causes a kernel crash during SMB connection recovery on affected releases. TCP_Server_Info.rlist is zeroed rather than initialized as an empty list, so list_add dereferences a null prev pointer; concurrent cifsd threads can also insert the same node twice. The flaw requires SMB client reconnection, and the published record does not establish an attacker-controlled trigger or an impact beyond service interruption.
Summary
What happened
A reconnect-list flaw in the Linux SMB client causes a kernel crash during SMB connection recovery on affected releases. TCP_Server_Info.rlist is zeroed rather than initialized as an empty list, so list_add dereferences a null prev pointer; concurrent cifsd threads can also insert the same node twice. The flaw requires SMB client reconnection, and the published record does not establish an attacker-controlled trigger or an impact beyond service interruption.
The record
- CVE
- CVE-2026-98174
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- 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=0 <6.12.112
- Affected versionversion=0 <6.18.54
- Affected versionversion=0 <6.6.158
- Affected versionversion=0 <7.2.8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <04082b1833856cb9ed87e0d3d5f04cbf836cf7da
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5a8f82f9c5839389cf4036029dd75a9911049e83
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5f270f091256da1338c3631083e15d7f83cc05e1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b5f924ffbfa976e4b97f17e8132c595b97482c2d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c037d6bde3dd5fa00b017b6b98a5389ec0ebc02f
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
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
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