Skip to main content
VulnerabilityPublished Updated

CVE-2026-64185: Linux kernel · sysfs: don't remove existing directory on update failure

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ccadd32cc1263802a5969c9efe0e96225450428c : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:03 UTC

Severity
Medium

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

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ c855cf2759d27142f771173d9fd8e7fdf9cf5138, < ccadd32cc1263802a5969c9efe0e96225450428c
Fixed in
  • ccadd32cc1263802a5969c9efe0e96225450428c
LinuxLinuxAffected
  • ≥ c855cf2759d27142f771173d9fd8e7fdf9cf5138, < c5e125c828b701afaf7493b42a14aa89362ff36d
Fixed in
  • c5e125c828b701afaf7493b42a14aa89362ff36d
LinuxLinuxAffected
  • ≥ c855cf2759d27142f771173d9fd8e7fdf9cf5138, < 237557b8a81ab948e8332f7c0058e758f081c0a3
Fixed in
  • 237557b8a81ab948e8332f7c0058e758f081c0a3
LinuxLinuxAffected
  • ≥ c855cf2759d27142f771173d9fd8e7fdf9cf5138, < 31527d80234caf83dc96ad478645e57df9de4472
Fixed in
  • 31527d80234caf83dc96ad478645e57df9de4472
LinuxLinuxAffected
  • ≥ c855cf2759d27142f771173d9fd8e7fdf9cf5138, < 708f6926f61f71e09b5e9fd668b9882ccd46e69f
Fixed in
  • 708f6926f61f71e09b5e9fd668b9882ccd46e69f
LinuxLinuxAffected
  • ≥ c855cf2759d27142f771173d9fd8e7fdf9cf5138, < 57b285e0368290aa55f79ba11419b96d0ebdb418
Fixed in
  • 57b285e0368290aa55f79ba11419b96d0ebdb418

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

Community reviews

Loading reviews…