{"api_version":"1","generated_at":"2026-08-15T08:44:36+00:00","cve":"CVE-2026-74359","urls":{"html":"https://cve.report/CVE-2026-74359","api":"https://cve.report/api/cve/CVE-2026-74359.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74359","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74359"},"summary":{"title":"configfs_lookup(): don't leave ->s_dentry dangling on failure","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nconfigfs_lookup(): don't leave ->s_dentry dangling on failure\n\nNormally ->s_dentry is cleared when dentry it's pointing to becomes\nnegative (on eviction, realistically).  However, that only happens\nif dentry gets to be positive in the first place; in case of inode\nallocation failure dentry never becomes positive, so ->d_iput()\nis not called at all.\n\nWe do part of what normally would've been done by configfs_d_iput()\n(dropping the reference to configfs_dirent) manually, but we do\nnot clear ->s_dentry there.  Sloppy as it is, it does not matter in\ncase of configfs_create_{dir,link}() - there configfs_dirent does\nnot survive dropping the sole reference to it.\n\nHowever, for configfs_lookup() it *does* survive, with a dangling\npointer to soon to be freed dentry sitting it its ->s_dentry.\n\nSubsequent getdents(2) in that directory will end up dereferencing\nthat pointer in order to pick the inode number.  Use after free...\n\nThis is the minimal fix; the right approach is to set the linkage\nbetween dentry and configfs_dirent only after we know that we have\nan inode, but that takes more surgery and the bug had been there\nsince 2006, so...","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:22:37","updated_at":"2026-08-15 06:22:37"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/eee07d769da5ac4e4f7bd0bc17828646a318d499","name":"https://git.kernel.org/stable/c/eee07d769da5ac4e4f7bd0bc17828646a318d499","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/57088b06109f3222963c639d8d743f42c2899b13","name":"https://git.kernel.org/stable/c/57088b06109f3222963c639d8d743f42c2899b13","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/3e83b2203aa59bd279e4f677ec793d49dc9d019e","name":"https://git.kernel.org/stable/c/3e83b2203aa59bd279e4f677ec793d49dc9d019e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9c747dcee164ead300de90550ad9e4122f0d1bbb","name":"https://git.kernel.org/stable/c/9c747dcee164ead300de90550ad9e4122f0d1bbb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/10da12d352b7b2bb330a8609fdda9a58bf0e9856","name":"https://git.kernel.org/stable/c/10da12d352b7b2bb330a8609fdda9a58bf0e9856","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c3b073a209a9baa691b744318ac929fecdd8847c","name":"https://git.kernel.org/stable/c/c3b073a209a9baa691b744318ac929fecdd8847c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b6e9c82522ddaa3ac0706b295ff4a71975d4f883","name":"https://git.kernel.org/stable/c/b6e9c82522ddaa3ac0706b295ff4a71975d4f883","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74359","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74359","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d 3e83b2203aa59bd279e4f677ec793d49dc9d019e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d b6e9c82522ddaa3ac0706b295ff4a71975d4f883 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d eee07d769da5ac4e4f7bd0bc17828646a318d499 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d 9c747dcee164ead300de90550ad9e4122f0d1bbb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d c3b073a209a9baa691b744318ac929fecdd8847c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d 57088b06109f3222963c639d8d743f42c2899b13 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3d0f89bb169482d26d5aa4e82e763077e7e9bc4d 10da12d352b7b2bb330a8609fdda9a58bf0e9856 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2.6.16","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 2.6.16 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.15.212 5.15.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.1.178 6.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.145 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.97 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.40 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/configfs/dir.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"3e83b2203aa59bd279e4f677ec793d49dc9d019e","status":"affected","version":"3d0f89bb169482d26d5aa4e82e763077e7e9bc4d","versionType":"git"},{"lessThan":"b6e9c82522ddaa3ac0706b295ff4a71975d4f883","status":"affected","version":"3d0f89bb169482d26d5aa4e82e763077e7e9bc4d","versionType":"git"},{"lessThan":"eee07d769da5ac4e4f7bd0bc17828646a318d499","status":"affected","version":"3d0f89bb169482d26d5aa4e82e763077e7e9bc4d","versionType":"git"},{"lessThan":"9c747dcee164ead300de90550ad9e4122f0d1bbb","status":"affected","version":"3d0f89bb169482d26d5aa4e82e763077e7e9bc4d","versionType":"git"},{"lessThan":"c3b073a209a9baa691b744318ac929fecdd8847c","status":"affected","version":"3d0f89bb169482d26d5aa4e82e763077e7e9bc4d","versionType":"git"},{"lessThan":"57088b06109f3222963c639d8d743f42c2899b13","status":"affected","version":"3d0f89bb169482d26d5aa4e82e763077e7e9bc4d","versionType":"git"},{"lessThan":"10da12d352b7b2bb330a8609fdda9a58bf0e9856","status":"affected","version":"3d0f89bb169482d26d5aa4e82e763077e7e9bc4d","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/configfs/dir.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"2.6.16"},{"lessThan":"2.6.16","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"5.15.*","status":"unaffected","version":"5.15.212","versionType":"semver"},{"lessThanOrEqual":"6.1.*","status":"unaffected","version":"6.1.178","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.145","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.97","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.40","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"5.15.212","versionStartIncluding":"2.6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.1.178","versionStartIncluding":"2.6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.145","versionStartIncluding":"2.6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.97","versionStartIncluding":"2.6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.40","versionStartIncluding":"2.6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"2.6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc1","versionStartIncluding":"2.6.16","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nconfigfs_lookup(): don't leave ->s_dentry dangling on failure\n\nNormally ->s_dentry is cleared when dentry it's pointing to becomes\nnegative (on eviction, realistically).  However, that only happens\nif dentry gets to be positive in the first place; in case of inode\nallocation failure dentry never becomes positive, so ->d_iput()\nis not called at all.\n\nWe do part of what normally would've been done by configfs_d_iput()\n(dropping the reference to configfs_dirent) manually, but we do\nnot clear ->s_dentry there.  Sloppy as it is, it does not matter in\ncase of configfs_create_{dir,link}() - there configfs_dirent does\nnot survive dropping the sole reference to it.\n\nHowever, for configfs_lookup() it *does* survive, with a dangling\npointer to soon to be freed dentry sitting it its ->s_dentry.\n\nSubsequent getdents(2) in that directory will end up dereferencing\nthat pointer in order to pick the inode number.  Use after free...\n\nThis is the minimal fix; the right approach is to set the linkage\nbetween dentry and configfs_dirent only after we know that we have\nan inode, but that takes more surgery and the bug had been there\nsince 2006, so..."}],"providerMetadata":{"dateUpdated":"2026-08-15T05:58:43.456Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/3e83b2203aa59bd279e4f677ec793d49dc9d019e"},{"url":"https://git.kernel.org/stable/c/b6e9c82522ddaa3ac0706b295ff4a71975d4f883"},{"url":"https://git.kernel.org/stable/c/eee07d769da5ac4e4f7bd0bc17828646a318d499"},{"url":"https://git.kernel.org/stable/c/9c747dcee164ead300de90550ad9e4122f0d1bbb"},{"url":"https://git.kernel.org/stable/c/c3b073a209a9baa691b744318ac929fecdd8847c"},{"url":"https://git.kernel.org/stable/c/57088b06109f3222963c639d8d743f42c2899b13"},{"url":"https://git.kernel.org/stable/c/10da12d352b7b2bb330a8609fdda9a58bf0e9856"}],"title":"configfs_lookup(): don't leave ->s_dentry dangling on failure","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74359","datePublished":"2026-08-15T05:58:43.456Z","dateReserved":"2026-08-15T05:44:03.887Z","dateUpdated":"2026-08-15T05:58:43.456Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 06:22:37","lastModifiedDate":"2026-08-15 06:22:37","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74359","Ordinal":"1","Title":"configfs_lookup(): don't leave ->s_dentry dangling on failure","CVE":"CVE-2026-74359","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74359","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nconfigfs_lookup(): don't leave ->s_dentry dangling on failure\n\nNormally ->s_dentry is cleared when dentry it's pointing to becomes\nnegative (on eviction, realistically).  However, that only happens\nif dentry gets to be positive in the first place; in case of inode\nallocation failure dentry never becomes positive, so ->d_iput()\nis not called at all.\n\nWe do part of what normally would've been done by configfs_d_iput()\n(dropping the reference to configfs_dirent) manually, but we do\nnot clear ->s_dentry there.  Sloppy as it is, it does not matter in\ncase of configfs_create_{dir,link}() - there configfs_dirent does\nnot survive dropping the sole reference to it.\n\nHowever, for configfs_lookup() it *does* survive, with a dangling\npointer to soon to be freed dentry sitting it its ->s_dentry.\n\nSubsequent getdents(2) in that directory will end up dereferencing\nthat pointer in order to pick the inode number.  Use after free...\n\nThis is the minimal fix; the right approach is to set the linkage\nbetween dentry and configfs_dirent only after we know that we have\nan inode, but that takes more surgery and the bug had been there\nsince 2006, so...","Type":"Description","Title":"configfs_lookup(): don't leave ->s_dentry dangling on failure"}]}}}