{"api_version":"1","generated_at":"2026-06-24T18:55:18+00:00","cve":"CVE-2026-53026","urls":{"html":"https://cve.report/CVE-2026-53026","api":"https://cve.report/api/cve/CVE-2026-53026.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53026","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53026"},"summary":{"title":"NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg\n\nIn nfsd4_add_rdaccess_to_wrdeleg, if fp->fi_fds[O_RDONLY] is already\nset by another thread, __nfs4_file_get_access should not be called\nto increment the nfs4_file access count since that was already done\nby the thread that added READ access to the file. The extra fi_access\ncount in nfs4_file can prevent the corresponding nfsd_file from being\nfreed.\n\nWhen stopping nfs-server service, these extra access counts trigger a\nBUG in kmem_cache_destroy() that shows nfsd_file object remaining on\n__kmem_cache_shutdown.\n\nThis problem can be reproduced by running the Git project's test\nsuite over NFS.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-24 17:17:13","updated_at":"2026-06-24 17:17:13"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/b48f44f36e6607b2f818560f19deb86b4a9c717b","name":"https://git.kernel.org/stable/c/b48f44f36e6607b2f818560f19deb86b4a9c717b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b81572b073441dfd32213e41857676d0dbff4665","name":"https://git.kernel.org/stable/c/b81572b073441dfd32213e41857676d0dbff4665","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/4584229395d0d65bd517780afe97ffea07cb2c3d","name":"https://git.kernel.org/stable/c/4584229395d0d65bd517780afe97ffea07cb2c3d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53026","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53026","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c07dc84ed67c5a182273171639bacbbb87c12175 4584229395d0d65bd517780afe97ffea07cb2c3d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8072e34e1387d03102b788677d491e2bcceef6f5 b81572b073441dfd32213e41857676d0dbff4665 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8072e34e1387d03102b788677d491e2bcceef6f5 b48f44f36e6607b2f818560f19deb86b4a9c717b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18.4 6.18.33 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.19","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.33 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.10 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * 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/nfs4state.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"4584229395d0d65bd517780afe97ffea07cb2c3d","status":"affected","version":"c07dc84ed67c5a182273171639bacbbb87c12175","versionType":"git"},{"lessThan":"b81572b073441dfd32213e41857676d0dbff4665","status":"affected","version":"8072e34e1387d03102b788677d491e2bcceef6f5","versionType":"git"},{"lessThan":"b48f44f36e6607b2f818560f19deb86b4a9c717b","status":"affected","version":"8072e34e1387d03102b788677d491e2bcceef6f5","versionType":"git"},{"lessThan":"6.18.33","status":"affected","version":"6.18.4","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/nfsd/nfs4state.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.19"},{"lessThan":"6.19","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.33","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.10","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.33","versionStartIncluding":"6.18.4","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.10","versionStartIncluding":"6.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"6.19","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg\n\nIn nfsd4_add_rdaccess_to_wrdeleg, if fp->fi_fds[O_RDONLY] is already\nset by another thread, __nfs4_file_get_access should not be called\nto increment the nfs4_file access count since that was already done\nby the thread that added READ access to the file. The extra fi_access\ncount in nfs4_file can prevent the corresponding nfsd_file from being\nfreed.\n\nWhen stopping nfs-server service, these extra access counts trigger a\nBUG in kmem_cache_destroy() that shows nfsd_file object remaining on\n__kmem_cache_shutdown.\n\nThis problem can be reproduced by running the Git project's test\nsuite over NFS."}],"providerMetadata":{"dateUpdated":"2026-06-24T16:29:34.855Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/4584229395d0d65bd517780afe97ffea07cb2c3d"},{"url":"https://git.kernel.org/stable/c/b81572b073441dfd32213e41857676d0dbff4665"},{"url":"https://git.kernel.org/stable/c/b48f44f36e6607b2f818560f19deb86b4a9c717b"}],"title":"NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53026","datePublished":"2026-06-24T16:29:34.855Z","dateReserved":"2026-06-09T07:44:35.379Z","dateUpdated":"2026-06-24T16:29:34.855Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-24 17:17:13","lastModifiedDate":"2026-06-24 17:17:13","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53026","Ordinal":"1","Title":"NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_","CVE":"CVE-2026-53026","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53026","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg\n\nIn nfsd4_add_rdaccess_to_wrdeleg, if fp->fi_fds[O_RDONLY] is already\nset by another thread, __nfs4_file_get_access should not be called\nto increment the nfs4_file access count since that was already done\nby the thread that added READ access to the file. The extra fi_access\ncount in nfs4_file can prevent the corresponding nfsd_file from being\nfreed.\n\nWhen stopping nfs-server service, these extra access counts trigger a\nBUG in kmem_cache_destroy() that shows nfsd_file object remaining on\n__kmem_cache_shutdown.\n\nThis problem can be reproduced by running the Git project's test\nsuite over NFS.","Type":"Description","Title":"NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_"}]}}}