In the Linux kernel, the following vulnerability has been resolved: ksmbd: require DELETE access for delete-on-close opens smb2open()…
CVE-2026-99750
In the Linux kernel, the following vulnerability has been resolved: ksmbd: require DELETE access for delete-on-close opens smb2open() accepts FILEDELETEONCLOSE on an existing file without DELETE in DesiredAccess. When the request asks only for FILEREADATTRIBUTES or READCONTROL, it also skips inodepermission() and the parent directory MAYWRITE | MAYEXEC 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 ksmbdinodeclose(), 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 STATUSDELETEPENDING. 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 MAXIMUMALLOWED 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…
Assessment
- CVSS
- Not yet scored
- Severity
- Unscored
- Known exploited
- Not listed in CISA KEV
- Exploit availability
- Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
- Published
- 20 November 2026
- Last updated
- 20 November 2026
- Assigner
- Linux
At the source
References
- https://git.kernel.org/stable/c/cc71e3abb81ae1470c09acae85d989b42509a2e0
- https://git.kernel.org/stable/c/2d0d4adb6bade8b204b10ad2a4c43f3b7d2af030
- https://git.kernel.org/stable/c/7e9a78223752911e118710009aab9dd9e10b2ee7
- https://git.kernel.org/stable/c/1dd91081ba3c692565f9c1f884149178d5a06d1e
- https://nvd.nist.gov/vuln/detail/CVE-2026-99750
Community proofs of concept
No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.
Submit a proof of concept
Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-99750