AZL-115639: CVE-2026-99750 affecting package kernel 6.6.161.1-1
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 directory, and the later permission checks are skipped as already done.
MS-FSA 2.1.5.1 requires an open with FILEDELETEONCLOSE and without DELETE in DesiredAccess to fail with STATUSINVALIDPARAMETER, and Samba does the same. Add that check to the CreateOptions validation, using the generic-mapped DesiredAccess so that GENERICALL still qualifies. This also refuses MAXIMUMALLOWED with FILEDELETEONCLOSE but no explicit DELETE, as MS-FSA and Samba do. When MAXIMUMALLOWED is requested with DELETE but the maximal access does not include DELETE, fail with STATUSACCESSDENIED. With DELETE requested, delete-on-close opens go through the existing parent directory check.