Shellfeed logo Shellfeed

CVE-2026-74359 · HIGH (CVSS 7.8)

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

Details

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

Severity

HIGH (CVSS 7.8) — vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

  • GIT git.kernel.org/pub/scm/linux/kernel/git/stable/linux [3d0f89bb169482d26d5aa4e82e763077e7e9bc4d – 3e83b2203aa59bd279e4f677ec793d49dc9d019e]
  • Linux Kernel [2.6.16 – 5.15.212] [5.16.0 – 6.1.178] [6.2.0 – 6.6.145] [6.7.0 – 6.12.97] [6.13.0 – 6.18.40] [6.19.0 – 7.1.5]

References