Answer in brief
CVE-2026-64185 records a Medium severity (CVSS 5.5) vulnerability in sysfs: don't remove existing directory on update failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c855cf2759d27142f771173d9fd8e7fdf9cf5138 <c5e125c828b701afaf7493b42a14aa89362ff36d || >=c855cf2759d27142f771173d9fd8e7fdf9cf5138 <ccadd32cc1263802a5969c9efe0e96225450428c || >=c855cf2759d27142f771173d9fd8e7fdf9cf5138 <14f2c14ae86c4af17a0a9f8ab46dacf2d5fd1d8a || >=c855cf2759d27142f771173d9fd8e7fdf9cf5138 <31527d80234caf83dc96ad478645e57df9de4472 || >=c855cf2759d27142f771173d9fd8e7fdf9cf5138 <57b285e0368290aa55f79ba11419b96d0ebdb418 || >=c855cf2759d27142f771173d9fd8e7fdf9cf5138 <48fa96538bd2868034d33429e4565fda384d0736 || >=c855cf2759d27142f771173d9fd8e7fdf9cf5138 <708f6926f61f71e09b5e9fd668b9882ccd46e69f || >=c855cf2759d27142f771173d9fd8e7fdf9cf5138 <237557b8a81ab948e8332f7c0058e758f081c0a3 | c5e125c828b701afaf7493b42a14aa89362ff36d, ccadd32cc1263802a5969c9efe0e96225450428c, 14f2c14ae86c4af17a0a9f8ab46dacf2d5fd1d8a, 31527d80234caf83dc96ad478645e57df9de4472, 57b285e0368290aa55f79ba11419b96d0ebdb418, 48fa96538bd2868034d33429e4565fda384d0736, 708f6926f61f71e09b5e9fd668b9882ccd46e69f, 237557b8a81ab948e8332f7c0058e758f081c0a3 |
| Linux/Linuxgeneric | 4.19 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
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.
Quoted source text, attributed separately from HOL analysis.