CVE-2026-74359
configfs_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...
INFO
Published Date :
Aug. 15, 2026, 6:22 a.m.
Last Modified :
Aug. 15, 2026, 6:22 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-74359
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the Linux kernel to the latest version.
- Review vendor security advisories for specific patch information.
- Restart affected services or systems after patching.
- Verify the fix by testing the affected functionality.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-74359.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-74359 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-74359
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-74359 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-74359 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 15, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '3d0f89bb169482d26d5aa4e82e763077e7e9bc4d', 'lessThan': '3e83b2203aa59bd279e4f677ec793d49dc9d019e', 'versionType': 'git'}, {'status': 'affected', 'version': '3d0f89bb169482d26d5aa4e82e763077e7e9bc4d', 'lessThan': 'b6e9c82522ddaa3ac0706b295ff4a71975d4f883', 'versionType': 'git'}, {'status': 'affected', 'version': '3d0f89bb169482d26d5aa4e82e763077e7e9bc4d', 'lessThan': 'eee07d769da5ac4e4f7bd0bc17828646a318d499', 'versionType': 'git'}, {'status': 'affected', 'version': '3d0f89bb169482d26d5aa4e82e763077e7e9bc4d', 'lessThan': '9c747dcee164ead300de90550ad9e4122f0d1bbb', 'versionType': 'git'}, {'status': 'affected', 'version': '3d0f89bb169482d26d5aa4e82e763077e7e9bc4d', 'lessThan': 'c3b073a209a9baa691b744318ac929fecdd8847c', 'versionType': 'git'}, {'status': 'affected', 'version': '3d0f89bb169482d26d5aa4e82e763077e7e9bc4d', 'lessThan': '57088b06109f3222963c639d8d743f42c2899b13', 'versionType': 'git'}, {'status': 'affected', 'version': '3d0f89bb169482d26d5aa4e82e763077e7e9bc4d', 'lessThan': '10da12d352b7b2bb330a8609fdda9a58bf0e9856', 'versionType': 'git'}], 'programFiles': ['fs/configfs/dir.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '2.6.16'}, {'status': 'unaffected', 'version': '0', 'lessThan': '2.6.16', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.15.212', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.97', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.40', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.5', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['fs/configfs/dir.c'], 'defaultStatus': 'affected'}] Added 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... Added Reference https://git.kernel.org/stable/c/10da12d352b7b2bb330a8609fdda9a58bf0e9856 Added Reference https://git.kernel.org/stable/c/3e83b2203aa59bd279e4f677ec793d49dc9d019e Added Reference https://git.kernel.org/stable/c/57088b06109f3222963c639d8d743f42c2899b13 Added Reference https://git.kernel.org/stable/c/9c747dcee164ead300de90550ad9e4122f0d1bbb Added Reference https://git.kernel.org/stable/c/b6e9c82522ddaa3ac0706b295ff4a71975d4f883 Added Reference https://git.kernel.org/stable/c/c3b073a209a9baa691b744318ac929fecdd8847c Added Reference https://git.kernel.org/stable/c/eee07d769da5ac4e4f7bd0bc17828646a318d499