CVE-2026-99750ksmbd: require DELETE access for delete-on-close opens
- —Not scoredno CVSS score yet
- —Exploitation in 30 daysno EPSS score yet
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: require DELETE access for delete-on-close opens smb2_open() accepts FILE_DELETE_ON_CLOSE on an existing file without DELETE in DesiredAccess. When the request asks only for FILE_READ_ATTRIBUTES or READ_CONTROL, it also skips inode_permission() and the parent directory MAY_WRITE | MAY_EXEC check that delete-on-close is meant to get. The file is then marked for deletion by a caller who could not delete it. The unlink happens later, in __ksmbd_inode_close(), when the last handle on the inode is closed, and it runs with the credentials of that handle. If the caller closes last, the unlink fails. If another user who can write the parent directory, such as the file's owner, still has the file open, the file is deleted when that user closes it. Until then new opens of the file fail with STATUS_DELETE_PENDING. So a user with only search permission on a directory can delete a file in it, or block opens of it, while the owner has it open. A MAXIMUM_ALLOWED open that also requests DELETE has the same problem. The requested access is replaced with the maximal access, which does not include DELETE when the caller cannot write the parent directory, and the later permission checks are skipped as already done. MS-FSA 2.1.5.1 requires an open with FILE_DELETE_ON_CLOSE and without DELETE in DesiredAccess to fail with STATUS_INVALID_PARAMETER, and Samba does the same. Add that check to the CreateOptions validation, using the generic-mapped DesiredAccess so that GENERIC_ALL still qualifies. This also refuses MAXIMUM_ALLOWED with FILE_DELETE_ON_CLOSE but no explicit DELETE, as MS-FSA and Samba do. When MAXIMUM_ALLOWED is requested with DELETE but the maximal access does not include DELETE, fail with STATUS_ACCESS_DENIED. With DELETE requested, delete-on-close opens go through the existing parent directory check.
Timeline
ID reserved
By Linux
- 56 days later
· 56 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE.
- EPSS (exploitation in 30 days)
- Not scored
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < cc71e3abb81ae1470c09acae85d989b42509a2e0
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 2d0d4adb6bade8b204b10ad2a4c43f3b7d2af030
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 7e9a78223752911e118710009aab9dd9e10b2ee7
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 1dd91081ba3c692565f9c1f884149178d5a06d1e
- affected 5.15
- unaffected < 5.15
- unaffected 6.12.118 – ≤ 6.12.*
- unaffected 6.18.64 – ≤ 6.18.*
- unaffected 7.3.5 – ≤ 7.3.*
- unaffected 7.4-rc2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/cc71e3abb81ae1470c09acae85d989b42509a2e0 (opens in a new tab)
- https://git.kernel.org/stable/c/2d0d4adb6bade8b204b10ad2a4c43f3b7d2af030 (opens in a new tab)
- https://git.kernel.org/stable/c/7e9a78223752911e118710009aab9dd9e10b2ee7 (opens in a new tab)
- https://git.kernel.org/stable/c/1dd91081ba3c692565f9c1f884149178d5a06d1e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99750)Record last updated .