What’s Vulnerable › Vulnerabilities
CVE-2026-64185: sysfs: don't remove existing directory on update failure
- Severity: medium (CVSS 5.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.1% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-07-19 · updated 2026-08-11
Description
In the Linux kernel, the following vulnerability has been resolved: sysfs: don't remove existing directory on update failure When sysfs_update_group() is called for a named group and create_files() fails (e.g. -ENOMEM), internal_create_group() calls kernfs_remove(kn) on the group directory. In the update path, kn was obtained via kernfs_find_and_get() and refers to a directory that already existed before this call. Removing it silently destroys a sysfs group that the caller did not create. Only remove the directory if we created it ourselves. On update failure the directory remains as it is left empty by remove_files() inside create_files(), but can be repopulated by a retry.
Affected products
- Linux kernel: from 4.19 before 5.10.258; from 5.11 before 5.15.209; from 5.16 before 6.1.175; from 6.2 before 6.6.142; from 6.7 before 6.12.92; from 6.13 before 6.18.34 — fixed in 5.10.258, 5.15.209, 6.1.175, 6.12.92, 6.18.34, 6.6.142
How to fix
Upgrade to a fixed version: Linux kernel 5.10.258, 5.15.209, 6.1.175, 6.12.92. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/14f2c14ae86c4af17a0a9f8ab46dacf2d5fd1d8a
- https://git.kernel.org/stable/c/237557b8a81ab948e8332f7c0058e758f081c0a3
- https://git.kernel.org/stable/c/31527d80234caf83dc96ad478645e57df9de4472
- https://git.kernel.org/stable/c/48fa96538bd2868034d33429e4565fda384d0736
- https://git.kernel.org/stable/c/57b285e0368290aa55f79ba11419b96d0ebdb418
- https://git.kernel.org/stable/c/708f6926f61f71e09b5e9fd668b9882ccd46e69f
- https://git.kernel.org/stable/c/c5e125c828b701afaf7493b42a14aa89362ff36d
- https://git.kernel.org/stable/c/ccadd32cc1263802a5969c9efe0e96225450428c
Get alerted when CVE-2026-64185 or the next vulnerability affects your stack