Kernel memory corruption via dangling configfs dentry
Published Aug 15, 2026 · Updated Aug 15, 2026
Use-after-free in Linux configfs allows local users to corrupt memory through a failed inode allocation during directory lookup. configfs_lookup leaves the surviving configfs_dirent s_dentry pointer uncleared when inode allocation fails, and a later getdents call dereferences the freed dentry for its inode number. Exploitation requires local access to a mounted configfs directory with a registered subsystem and can corrupt kernel memory or crash the system.
Summary
What happened
Use-after-free in Linux configfs allows local users to corrupt memory through a failed inode allocation during directory lookup. configfs_lookup leaves the surviving configfs_dirent s_dentry pointer uncleared when inode allocation fails, and a later getdents call dereferences the freed dentry for its inode number. Exploitation requires local access to a mounted configfs directory with a registered subsystem and can corrupt kernel memory or crash the system.
The record
- CVE
- CVE-2026-74359
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-825, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.16
- Affected versionversion=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <10da12d352b7b2bb330a8609fdda9a58bf0e9856
- Affected versionversion=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <3e83b2203aa59bd279e4f677ec793d49dc9d019e
- Affected versionversion=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <57088b06109f3222963c639d8d743f42c2899b13
- Affected versionversion=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <9c747dcee164ead300de90550ad9e4122f0d1bbb
- Affected versionversion=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <b6e9c82522ddaa3ac0706b295ff4a71975d4f883
- Affected versionversion=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <c3b073a209a9baa691b744318ac929fecdd8847c
- Affected versionversion=3d0f89bb169482d26d5aa4e82e763077e7e9bc4d <eee07d769da5ac4e4f7bd0bc17828646a318d499
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo