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-97949configfs: unhash the dentry before dropping the item in rmdir

Description

In the Linux kernel, the following vulnerability has been resolved: configfs: unhash the dentry before dropping the item in rmdir configfs_get_config_item() treats a hashed dentry as proof that sd->s_element is a live config_item. configfs_rmdir() breaks that: simple_rmdir() leaves the dentry hashed, the last reference to the item is dropped right after, and the dentry is only unhashed by d_delete() once ->rmdir() has returned. configfs_symlink() resolves its target holding no lock on it, so get_target() can land in that window: BUG: KASAN: slab-use-after-free in config_item_get+0x26/0x90 get_target fs/configfs/symlink.c:128 [inline] configfs_symlink+0x4ab/0x1030 fs/configfs/symlink.c:185 Unhash in configfs_remove_dir(), while the item is still guaranteed to be there. A reference obtained just before that stays harmless, as create_link() rechecks CONFIGFS_USET_DROPPING, already set by configfs_detach_prep(). Both configfs_unregister_subsystem() paths d_drop() after detaching, so this only makes rmdir match them.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 26 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (18 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < b315d865660766d45ecdbf7433a4e3d36a554b3b
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < 446720051d44eebaa81b33969173160057b73a33
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < 5d7cbfb65e47cc71d5d94d87d5d0d1679080f3eb
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < 925d8564f1b2d9b46c5ab63b9bc942cea006da9b
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < f06c2d26d1999d37e93299db0ecead04ca7d0b9f
  • Linux · Linux

    • affected 2.6.16
    • unaffected < 2.6.16
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .