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-97950configfs: pin the symlink target's dirent instead of chasing ->ci_dentry

Description

In the Linux kernel, the following vulnerability has been resolved: configfs: pin the symlink target's dirent instead of chasing ->ci_dentry create_link() reads the target's configfs_dirent from item->ci_dentry->d_fsdata, relying on the item reference taken by get_target(). That reference pins the item, not its dentry: the dentry is pinned by DCACHE_PERSISTENT, which configfs_remove_dir() releases via simple_rmdir() while the item is still alive. A symlink racing with rmdir of its target can therefore find ->ci_dentry freed and its dirent released, triggering WARN_ON(!atomic_read(&sd->s_count)) in configfs_get(). Take the dirent in get_target() as well, under ->d_lock and atomically with the item reference, and pass it down to create_link(). A hashed dentry has not been killed yet, so its ->d_fsdata reference keeps the dirent alive there.

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.21% · top 89% of all CVEs (13 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 – < a44744454eafbc158e8c8e3ef8d207076410b195
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < 846ff40fd57a47e59a41f4e331ec3b34efaddc23
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < 4f54beb2e7f6d399396466682fba3539bcdcb414
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < d47c5de1cd6bfbe1067fc310bf90e4e00205e839
    • affected 7063fbf2261194f72ee75afca67b3b38b554b5fa – < a7c1290eef60711c10289c056ad32ed1f2b47b12
  • 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-97950 badge
[![CVE-2026-97950](https://cveledger.app/badge/CVE-2026-97950.svg)](https://cveledger.app/cve/CVE-2026-97950)

Record last updated .