CVE-2026-64185: Linux kernel · sysfs: don't remove existing directory on update failure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ccadd32cc1263802a5969c9efe0e96225450428c : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:03 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in ccadd32cc1263802a5969c9efe0e96225450428c, c5e125c828b701afaf7493b42a14aa89362ff36d, 237557b8a81ab948e8332f7c0058e758f081c0a3 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 6 Nov 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
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel versions identified by the provided commit hashes. Users and maintainers should update to these fixed versions to remediate the issue.
Description
A vulnerability in the Linux kernel sysfs subsystem could cause the removal of an existing sysfs directory during an update failure. Specifically, when sysfs_update_group() is called and create_files() fails, the kernel may incorrectly remove a directory that existed prior to the update attempt. This could lead to unintended destruction of sysfs groups not created by the caller. The issue has been fixed by ensuring the directory is only removed if it was created during the update attempt.
References
- git.kernel.org/stable/c/c5e125c828b701afaf7493b42a14aa89362ff36d (opens in a new tab)
- git.kernel.org/stable/c/ccadd32cc1263802a5969c9efe0e96225450428c (opens in a new tab)
- git.kernel.org/stable/c/14f2c14ae86c4af17a0a9f8ab46dacf2d5fd1d8a (opens in a new tab)
- git.kernel.org/stable/c/31527d80234caf83dc96ad478645e57df9de4472 (opens in a new tab)
- git.kernel.org/stable/c/57b285e0368290aa55f79ba11419b96d0ebdb418 (opens in a new tab)
- git.kernel.org/stable/c/48fa96538bd2868034d33429e4565fda384d0736 (opens in a new tab)
- git.kernel.org/stable/c/708f6926f61f71e09b5e9fd668b9882ccd46e69f (opens in a new tab)
- git.kernel.org/stable/c/237557b8a81ab948e8332f7c0058e758f081c0a3 (opens in a new tab)