CVE-2026-64185
sysfs: don't remove existing directory on update failure
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.
INFO
Published Date :
July 19, 2026, 4:18 p.m.
Last Modified :
July 19, 2026, 4:18 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64185
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Apply the Linux kernel patch for sysfs directory update.
- Verify sysfs directory integrity after updates.
- Ensure proper error handling for sysfs group creation.
- Test update operations thoroughly.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64185.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64185 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64185
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64185 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64185 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 19, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'c855cf2759d27142f771173d9fd8e7fdf9cf5138', 'lessThan': 'c5e125c828b701afaf7493b42a14aa89362ff36d', 'versionType': 'git'}, {'status': 'affected', 'version': 'c855cf2759d27142f771173d9fd8e7fdf9cf5138', 'lessThan': 'ccadd32cc1263802a5969c9efe0e96225450428c', 'versionType': 'git'}, {'status': 'affected', 'version': 'c855cf2759d27142f771173d9fd8e7fdf9cf5138', 'lessThan': '14f2c14ae86c4af17a0a9f8ab46dacf2d5fd1d8a', 'versionType': 'git'}, {'status': 'affected', 'version': 'c855cf2759d27142f771173d9fd8e7fdf9cf5138', 'lessThan': '31527d80234caf83dc96ad478645e57df9de4472', 'versionType': 'git'}, {'status': 'affected', 'version': 'c855cf2759d27142f771173d9fd8e7fdf9cf5138', 'lessThan': '57b285e0368290aa55f79ba11419b96d0ebdb418', 'versionType': 'git'}, {'status': 'affected', 'version': 'c855cf2759d27142f771173d9fd8e7fdf9cf5138', 'lessThan': '48fa96538bd2868034d33429e4565fda384d0736', 'versionType': 'git'}, {'status': 'affected', 'version': 'c855cf2759d27142f771173d9fd8e7fdf9cf5138', 'lessThan': '708f6926f61f71e09b5e9fd668b9882ccd46e69f', 'versionType': 'git'}, {'status': 'affected', 'version': 'c855cf2759d27142f771173d9fd8e7fdf9cf5138', 'lessThan': '237557b8a81ab948e8332f7c0058e758f081c0a3', 'versionType': 'git'}], 'programFiles': ['fs/sysfs/group.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4.19'}, {'status': 'unaffected', 'version': '0', 'lessThan': '4.19', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.258', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.209', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.175', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.142', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.92', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.34', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.11', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['fs/sysfs/group.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/14f2c14ae86c4af17a0a9f8ab46dacf2d5fd1d8a Added Reference https://git.kernel.org/stable/c/237557b8a81ab948e8332f7c0058e758f081c0a3 Added Reference https://git.kernel.org/stable/c/31527d80234caf83dc96ad478645e57df9de4472 Added Reference https://git.kernel.org/stable/c/48fa96538bd2868034d33429e4565fda384d0736 Added Reference https://git.kernel.org/stable/c/57b285e0368290aa55f79ba11419b96d0ebdb418 Added Reference https://git.kernel.org/stable/c/708f6926f61f71e09b5e9fd668b9882ccd46e69f Added Reference https://git.kernel.org/stable/c/c5e125c828b701afaf7493b42a14aa89362ff36d Added Reference https://git.kernel.org/stable/c/ccadd32cc1263802a5969c9efe0e96225450428c