{"api_version":"1","generated_at":"2026-09-11T21:38:11+00:00","cve":"CVE-2026-89677","urls":{"html":"https://cve.report/CVE-2026-89677","api":"https://cve.report/api/cve/CVE-2026-89677.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-89677","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-89677"},"summary":{"title":"nfsd: fix possible fh_compose of wrong dentry in nfsd4_create_file()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: fix possible fh_compose of wrong dentry in nfsd4_create_file()\n\ndentry_create() can hypothetically provide a different dentry than the\none passed in.  This could happen, for example, if the exported\nfilesystem is NFS, and the server returned to OPEN a filehandle which\nmatched a directory that was already in the dcache.  Clearly this would\nnot be expected!\n\nIf this were to happen the dentry (child) that was already stored in\nresfhp could be freed and later dereferenced.\n\nWe shouldn't call fh_compose() until we are certain that we have the\nfinal dentry, so this patch moved the fh_compose() call to two places:\none for the case where the target already exists, and one after\ndentry_create() where it was created.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:19:54","updated_at":"2026-09-11 20:19:54"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/3e2c79360c6a89975ec5b5a7d4ef937e4db91a27","name":"https://git.kernel.org/stable/c/3e2c79360c6a89975ec5b5a7d4ef937e4db91a27","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/033e783709ce99662cf81f6abcad746a8da9d35f","name":"https://git.kernel.org/stable/c/033e783709ce99662cf81f6abcad746a8da9d35f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-89677","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89677","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 64a989dbd144e0622371396461b11335459692d2 033e783709ce99662cf81f6abcad746a8da9d35f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 64a989dbd144e0622371396461b11335459692d2 3e2c79360c6a89975ec5b5a7d4ef937e4db91a27 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.4 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-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/nfsd/nfs4proc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"033e783709ce99662cf81f6abcad746a8da9d35f","status":"affected","version":"64a989dbd144e0622371396461b11335459692d2","versionType":"git"},{"lessThan":"3e2c79360c6a89975ec5b5a7d4ef937e4db91a27","status":"affected","version":"64a989dbd144e0622371396461b11335459692d2","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/nfsd/nfs4proc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.0"},{"lessThan":"7.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.4","versionStartIncluding":"7.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"7.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: fix possible fh_compose of wrong dentry in nfsd4_create_file()\n\ndentry_create() can hypothetically provide a different dentry than the\none passed in.  This could happen, for example, if the exported\nfilesystem is NFS, and the server returned to OPEN a filehandle which\nmatched a directory that was already in the dcache.  Clearly this would\nnot be expected!\n\nIf this were to happen the dentry (child) that was already stored in\nresfhp could be freed and later dereferenced.\n\nWe shouldn't call fh_compose() until we are certain that we have the\nfinal dentry, so this patch moved the fh_compose() call to two places:\none for the case where the target already exists, and one after\ndentry_create() where it was created."}],"providerMetadata":{"dateUpdated":"2026-09-11T19:46:01.185Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/033e783709ce99662cf81f6abcad746a8da9d35f"},{"url":"https://git.kernel.org/stable/c/3e2c79360c6a89975ec5b5a7d4ef937e4db91a27"}],"title":"nfsd: fix possible fh_compose of wrong dentry in nfsd4_create_file()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-89677","datePublished":"2026-09-11T19:46:01.185Z","dateReserved":"2026-09-11T19:38:34.747Z","dateUpdated":"2026-09-11T19:46:01.185Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:19:54","lastModifiedDate":"2026-09-11 20:19:54","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"89677","Ordinal":"1","Title":"nfsd: fix possible fh_compose of wrong dentry in nfsd4_create_fi","CVE":"CVE-2026-89677","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"89677","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: fix possible fh_compose of wrong dentry in nfsd4_create_file()\n\ndentry_create() can hypothetically provide a different dentry than the\none passed in.  This could happen, for example, if the exported\nfilesystem is NFS, and the server returned to OPEN a filehandle which\nmatched a directory that was already in the dcache.  Clearly this would\nnot be expected!\n\nIf this were to happen the dentry (child) that was already stored in\nresfhp could be freed and later dereferenced.\n\nWe shouldn't call fh_compose() until we are certain that we have the\nfinal dentry, so this patch moved the fh_compose() call to two places:\none for the case where the target already exists, and one after\ndentry_create() where it was created.","Type":"Description","Title":"nfsd: fix possible fh_compose of wrong dentry in nfsd4_create_fi"}]}}}