Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64185sysfs: 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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64185, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 – < c5e125c828b701afaf7493b42a14aa89362ff36d
    • affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 – < ccadd32cc1263802a5969c9efe0e96225450428c
    • affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 – < 14f2c14ae86c4af17a0a9f8ab46dacf2d5fd1d8a
    • affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 – < 31527d80234caf83dc96ad478645e57df9de4472
    • affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 – < 57b285e0368290aa55f79ba11419b96d0ebdb418
    • affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 – < 48fa96538bd2868034d33429e4565fda384d0736
    • affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 – < 708f6926f61f71e09b5e9fd668b9882ccd46e69f
    • affected c855cf2759d27142f771173d9fd8e7fdf9cf5138 – < 237557b8a81ab948e8332f7c0058e758f081c0a3
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.142 – ≤ 6.6.*
    • unaffected 6.12.92 – ≤ 6.12.*
    • unaffected 6.18.34 – ≤ 6.18.*
    • unaffected 7.0.11 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64185 badge
[![CVE-2026-64185](https://cveledger.app/badge/CVE-2026-64185.svg)](https://cveledger.app/cve/CVE-2026-64185)

Record last updated .