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-74359configfs_lookup(): don't leave ->s_dentry dangling on failure

Description

In the Linux kernel, the following vulnerability has been resolved: configfs_lookup(): don't leave ->s_dentry dangling on failure Normally ->s_dentry is cleared when dentry it's pointing to becomes negative (on eviction, realistically). However, that only happens if dentry gets to be positive in the first place; in case of inode allocation failure dentry never becomes positive, so ->d_iput() is not called at all. We do part of what normally would've been done by configfs_d_iput() (dropping the reference to configfs_dirent) manually, but we do not clear ->s_dentry there. Sloppy as it is, it does not matter in case of configfs_create_{dir,link}() - there configfs_dirent does not survive dropping the sole reference to it. However, for configfs_lookup() it *does* survive, with a dangling pointer to soon to be freed dentry sitting it its ->s_dentry. Subsequent getdents(2) in that directory will end up dereferencing that pointer in order to pick the inode number. Use after free... This is the minimal fix; the right approach is to set the linkage between dentry and configfs_dirent only after we know that we have an inode, but that takes more surgery and the bug had been there since 2006, so...

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 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-74359, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d – < 3e83b2203aa59bd279e4f677ec793d49dc9d019e
    • affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d – < b6e9c82522ddaa3ac0706b295ff4a71975d4f883
    • affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d – < eee07d769da5ac4e4f7bd0bc17828646a318d499
    • affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d – < 9c747dcee164ead300de90550ad9e4122f0d1bbb
    • affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d – < c3b073a209a9baa691b744318ac929fecdd8847c
    • affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d – < 57088b06109f3222963c639d8d743f42c2899b13
    • affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d – < 10da12d352b7b2bb330a8609fdda9a58bf0e9856
  • Linux · Linux

    • affected 2.6.16
    • unaffected < 2.6.16
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .