sysfs: don't remove existing directory on update failure
Summary
| CVE | CVE-2026-64185 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-19 16:18:00 UTC |
| Updated | 2026-07-19 16:18:00 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 c5e125c828b701afaf7493b42a14aa89362ff36d git |
Not specified |
| CNA |
Linux |
Linux |
affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 ccadd32cc1263802a5969c9efe0e96225450428c git |
Not specified |
| CNA |
Linux |
Linux |
affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 14f2c14ae86c4af17a0a9f8ab46dacf2d5fd1d8a git |
Not specified |
| CNA |
Linux |
Linux |
affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 31527d80234caf83dc96ad478645e57df9de4472 git |
Not specified |
| CNA |
Linux |
Linux |
affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 57b285e0368290aa55f79ba11419b96d0ebdb418 git |
Not specified |
| CNA |
Linux |
Linux |
affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 48fa96538bd2868034d33429e4565fda384d0736 git |
Not specified |
| CNA |
Linux |
Linux |
affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 708f6926f61f71e09b5e9fd668b9882ccd46e69f git |
Not specified |
| CNA |
Linux |
Linux |
affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 237557b8a81ab948e8332f7c0058e758f081c0a3 git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.19 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.19 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10.258 5.10.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.209 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.175 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.142 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.92 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.34 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0.11 7.0.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/237557b8a81ab948e8332f7c0058e758f081c0a3 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/708f6926f61f71e09b5e9fd668b9882ccd46e69f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/48fa96538bd2868034d33429e4565fda384d0736 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ccadd32cc1263802a5969c9efe0e96225450428c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/31527d80234caf83dc96ad478645e57df9de4472 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/57b285e0368290aa55f79ba11419b96d0ebdb418 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/14f2c14ae86c4af17a0a9f8ab46dacf2d5fd1d8a |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c5e125c828b701afaf7493b42a14aa89362ff36d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.