Answer in brief
CVE-2026-74359 records a High severity (CVSS 7.8) vulnerability in configfs_lookup(): don't leave ->s_dentry dangling on failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <3e83b2203aa59bd279e4f677ec793d49dc9d019e || >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <b6e9c82522ddaa3ac0706b295ff4a71975d4f883 || >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <eee07d769da5ac4e4f7bd0bc17828646a318d499 || >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <9c747dcee164ead300de90550ad9e4122f0d1bbb || >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <c3b073a209a9baa691b744318ac929fecdd8847c || >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <57088b06109f3222963c639d8d743f42c2899b13 || >=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <10da12d352b7b2bb330a8609fdda9a58bf0e9856 | 3e83b2203aa59bd279e4f677ec793d49dc9d019e, b6e9c82522ddaa3ac0706b295ff4a71975d4f883, eee07d769da5ac4e4f7bd0bc17828646a318d499, 9c747dcee164ead300de90550ad9e4122f0d1bbb, c3b073a209a9baa691b744318ac929fecdd8847c, 57088b06109f3222963c639d8d743f42c2899b13, 10da12d352b7b2bb330a8609fdda9a58bf0e9856 |
| Linux/Linuxgeneric | 2.6.16 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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...
Quoted source text, attributed separately from HOL analysis.