CVE-2026-98175: Linux kernel · smb: client: cancel reconnect work in clean_demultiplex_info()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in e3f6a779433d13aafb5edab59e4f9313051e8a52 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e3f6a779433d13aafb5edab59e4f9313051e8a52, c65eae6f61d1778ff7a82e4aae4080e26f486af1, 180380272f116dbd2b0354c5c7872e112e519149 +10
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in Linux kernel versions 4.10 and several stable branches including 3.17, 3.19, 4.2, 4.5, and 4.9. Users and administrators should upgrade to these fixed versions or later to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-98175 is a use-after-free vulnerability in the Linux kernel's SMB client implementation. The flaw occurs because the reconnect delayed work is not canceled in the clean_demultiplex_info() function before the server structure is freed, leading to potential use-after-free when reconnect work executes later. This issue affects multiple Linux kernel versions prior to 4.10 and related stable branches. The vulnerability has been fixed by ensuring the reconnect work is canceled before freeing the server.
References
- git.kernel.org/stable/c/180380272f116dbd2b0354c5c7872e112e519149 (opens in a new tab)
- git.kernel.org/stable/c/e3f6a779433d13aafb5edab59e4f9313051e8a52 (opens in a new tab)
- git.kernel.org/stable/c/7ab9ceedd860216fb97f2d8574cbe58b8906f42a (opens in a new tab)
- git.kernel.org/stable/c/2e5103e11a17c274715dd56cf185eeedccf686b8 (opens in a new tab)
- git.kernel.org/stable/c/c65eae6f61d1778ff7a82e4aae4080e26f486af1 (opens in a new tab)