CVE-2026-74359

published 15 Aug 2026 · updated 15 Nov 2026

configfs_lookup(): don't leave ->s_dentry dangling on failure

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel eee07d769da5ac4e4f7bd0bc17828646a318d499, Kernel 10da12d352b7b2bb330a8609fdda9a58bf0e9856, Kernel 3e83b2203aa59bd279e4f677ec793d49dc9d019e and 10 more.

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...

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <eee07d769da5ac4e4f7bd0bc17828646a318d499, >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <10da12d352b7b2bb330a8609fdda9a58bf0e9856, >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <3e83b2203aa59bd279e4f677ec793d49dc9d019e, >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <57088b06109f3222963c639d8d743f42c2899b13, >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <9c747dcee164ead300de90550ad9e4122f0d1bbb, >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <b6e9c82522ddaa3ac0706b295ff4a71975d4f883, >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <c3b073a209a9baa691b744318ac929fecdd8847c, =2.6.16eee07d769da5ac4e4f7bd0bc17828646a318d499, 10da12d352b7b2bb330a8609fdda9a58bf0e9856, 3e83b2203aa59bd279e4f677ec793d49dc9d019e, 57088b06109f3222963c639d8d743f42c2899b13, 9c747dcee164ead300de90550ad9e4122f0d1bbb, b6e9c82522ddaa3ac0706b295ff4a71975d4f883, c3b073a209a9baa691b744318ac929fecdd8847c
linux-kernel: Kernel>=5.16.0 <6.1.178, >=6.13.0 <6.18.40, >=6.19.0 <7.1.5, >=6.2.0 <6.6.145, >=6.7.0 <6.12.97, >=2.6.16 <5.15.2126.1.178, 6.18.40, 7.1.5, 6.6.145, 6.12.97, 5.15.212

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-74359 severity on Zeptric[![CVE-2026-74359](https://zeptric.io/badge/cve/CVE-2026-74359.svg)](https://zeptric.io/cve/CVE-2026-74359)