{"api_version":"1","generated_at":"2026-11-20T07:30:05+00:00","cve":"CVE-2026-99750","urls":{"html":"https://cve.report/CVE-2026-99750","api":"https://cve.report/api/cve/CVE-2026-99750.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99750","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99750"},"summary":{"title":"ksmbd: require DELETE access for delete-on-close opens","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: require DELETE access for delete-on-close opens\n\nsmb2_open() accepts FILE_DELETE_ON_CLOSE on an existing file without\nDELETE in DesiredAccess. When the request asks only for\nFILE_READ_ATTRIBUTES or READ_CONTROL, it also skips inode_permission()\nand the parent directory MAY_WRITE | MAY_EXEC check that delete-on-close\nis meant to get. The file is then marked for deletion by a caller who\ncould not delete it.\n\nThe unlink happens later, in __ksmbd_inode_close(), when the last handle\non the inode is closed, and it runs with the credentials of that handle.\nIf the caller closes last, the unlink fails. If another user who can\nwrite the parent directory, such as the file's owner, still has the file\nopen, the file is deleted when that user closes it. Until then new opens\nof the file fail with STATUS_DELETE_PENDING. So a user with only search\npermission on a directory can delete a file in it, or block opens of it,\nwhile the owner has it open.\n\nA MAXIMUM_ALLOWED open that also requests DELETE has the same problem.\nThe requested access is replaced with the maximal access, which does not\ninclude DELETE when the caller cannot write the parent directory, and the\nlater permission checks are skipped as already done.\n\nMS-FSA 2.1.5.1 requires an open with FILE_DELETE_ON_CLOSE and without\nDELETE in DesiredAccess to fail with STATUS_INVALID_PARAMETER, and Samba\ndoes the same. Add that check to the CreateOptions validation, using\nthe generic-mapped DesiredAccess so that GENERIC_ALL still qualifies.\nThis also refuses MAXIMUM_ALLOWED with FILE_DELETE_ON_CLOSE but no\nexplicit DELETE, as MS-FSA and Samba do. When MAXIMUM_ALLOWED is\nrequested with DELETE but the maximal access does not include DELETE,\nfail with STATUS_ACCESS_DENIED. With DELETE requested, delete-on-close\nopens go through the existing parent directory check.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:12","updated_at":"2026-11-20 06:18:12"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/cc71e3abb81ae1470c09acae85d989b42509a2e0","name":"https://git.kernel.org/stable/c/cc71e3abb81ae1470c09acae85d989b42509a2e0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7e9a78223752911e118710009aab9dd9e10b2ee7","name":"https://git.kernel.org/stable/c/7e9a78223752911e118710009aab9dd9e10b2ee7","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2d0d4adb6bade8b204b10ad2a4c43f3b7d2af030","name":"https://git.kernel.org/stable/c/2d0d4adb6bade8b204b10ad2a4c43f3b7d2af030","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1dd91081ba3c692565f9c1f884149178d5a06d1e","name":"https://git.kernel.org/stable/c/1dd91081ba3c692565f9c1f884149178d5a06d1e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99750","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99750","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 cc71e3abb81ae1470c09acae85d989b42509a2e0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 2d0d4adb6bade8b204b10ad2a4c43f3b7d2af030 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 7e9a78223752911e118710009aab9dd9e10b2ee7 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 1dd91081ba3c692565f9c1f884149178d5a06d1e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.15 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.118 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.64 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * 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/smb/server/smb2pdu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"cc71e3abb81ae1470c09acae85d989b42509a2e0","status":"affected","version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","versionType":"git"},{"lessThan":"2d0d4adb6bade8b204b10ad2a4c43f3b7d2af030","status":"affected","version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","versionType":"git"},{"lessThan":"7e9a78223752911e118710009aab9dd9e10b2ee7","status":"affected","version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","versionType":"git"},{"lessThan":"1dd91081ba3c692565f9c1f884149178d5a06d1e","status":"affected","version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/smb/server/smb2pdu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.15"},{"lessThan":"5.15","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.118","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.64","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.118","versionStartIncluding":"5.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.64","versionStartIncluding":"5.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"5.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"5.15","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: require DELETE access for delete-on-close opens\n\nsmb2_open() accepts FILE_DELETE_ON_CLOSE on an existing file without\nDELETE in DesiredAccess. When the request asks only for\nFILE_READ_ATTRIBUTES or READ_CONTROL, it also skips inode_permission()\nand the parent directory MAY_WRITE | MAY_EXEC check that delete-on-close\nis meant to get. The file is then marked for deletion by a caller who\ncould not delete it.\n\nThe unlink happens later, in __ksmbd_inode_close(), when the last handle\non the inode is closed, and it runs with the credentials of that handle.\nIf the caller closes last, the unlink fails. If another user who can\nwrite the parent directory, such as the file's owner, still has the file\nopen, the file is deleted when that user closes it. Until then new opens\nof the file fail with STATUS_DELETE_PENDING. So a user with only search\npermission on a directory can delete a file in it, or block opens of it,\nwhile the owner has it open.\n\nA MAXIMUM_ALLOWED open that also requests DELETE has the same problem.\nThe requested access is replaced with the maximal access, which does not\ninclude DELETE when the caller cannot write the parent directory, and the\nlater permission checks are skipped as already done.\n\nMS-FSA 2.1.5.1 requires an open with FILE_DELETE_ON_CLOSE and without\nDELETE in DesiredAccess to fail with STATUS_INVALID_PARAMETER, and Samba\ndoes the same. Add that check to the CreateOptions validation, using\nthe generic-mapped DesiredAccess so that GENERIC_ALL still qualifies.\nThis also refuses MAXIMUM_ALLOWED with FILE_DELETE_ON_CLOSE but no\nexplicit DELETE, as MS-FSA and Samba do. When MAXIMUM_ALLOWED is\nrequested with DELETE but the maximal access does not include DELETE,\nfail with STATUS_ACCESS_DENIED. With DELETE requested, delete-on-close\nopens go through the existing parent directory check."}],"providerMetadata":{"dateUpdated":"2026-11-20T05:51:20.619Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/cc71e3abb81ae1470c09acae85d989b42509a2e0"},{"url":"https://git.kernel.org/stable/c/2d0d4adb6bade8b204b10ad2a4c43f3b7d2af030"},{"url":"https://git.kernel.org/stable/c/7e9a78223752911e118710009aab9dd9e10b2ee7"},{"url":"https://git.kernel.org/stable/c/1dd91081ba3c692565f9c1f884149178d5a06d1e"}],"title":"ksmbd: require DELETE access for delete-on-close opens","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99750","datePublished":"2026-11-20T05:51:20.619Z","dateReserved":"2026-09-25T10:25:14.432Z","dateUpdated":"2026-11-20T05:51:20.619Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:12","lastModifiedDate":"2026-11-20 06:18:12","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99750","Ordinal":"1","Title":"ksmbd: require DELETE access for delete-on-close opens","CVE":"CVE-2026-99750","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99750","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: require DELETE access for delete-on-close opens\n\nsmb2_open() accepts FILE_DELETE_ON_CLOSE on an existing file without\nDELETE in DesiredAccess. When the request asks only for\nFILE_READ_ATTRIBUTES or READ_CONTROL, it also skips inode_permission()\nand the parent directory MAY_WRITE | MAY_EXEC check that delete-on-close\nis meant to get. The file is then marked for deletion by a caller who\ncould not delete it.\n\nThe unlink happens later, in __ksmbd_inode_close(), when the last handle\non the inode is closed, and it runs with the credentials of that handle.\nIf the caller closes last, the unlink fails. If another user who can\nwrite the parent directory, such as the file's owner, still has the file\nopen, the file is deleted when that user closes it. Until then new opens\nof the file fail with STATUS_DELETE_PENDING. So a user with only search\npermission on a directory can delete a file in it, or block opens of it,\nwhile the owner has it open.\n\nA MAXIMUM_ALLOWED open that also requests DELETE has the same problem.\nThe requested access is replaced with the maximal access, which does not\ninclude DELETE when the caller cannot write the parent directory, and the\nlater permission checks are skipped as already done.\n\nMS-FSA 2.1.5.1 requires an open with FILE_DELETE_ON_CLOSE and without\nDELETE in DesiredAccess to fail with STATUS_INVALID_PARAMETER, and Samba\ndoes the same. Add that check to the CreateOptions validation, using\nthe generic-mapped DesiredAccess so that GENERIC_ALL still qualifies.\nThis also refuses MAXIMUM_ALLOWED with FILE_DELETE_ON_CLOSE but no\nexplicit DELETE, as MS-FSA and Samba do. When MAXIMUM_ALLOWED is\nrequested with DELETE but the maximal access does not include DELETE,\nfail with STATUS_ACCESS_DENIED. With DELETE requested, delete-on-close\nopens go through the existing parent directory check.","Type":"Description","Title":"ksmbd: require DELETE access for delete-on-close opens"}]}}}