ksmbd: enforce the read-only share flag when creating a stream
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 09139429fab3a5114c18d7c15fb161511d4d66c9, Kernel ece35b45ec17a462cc5947ad4fbc3450657aa55b and Kernel 7.3.5.
In the Linux kernel, the following vulnerability has been resolved: ksmbd: enforce the read-only share flag when creating a stream When a share is read-only, smb2_open() rejects opens that would create or truncate a file. Creating a named stream on an existing file with streams_xattr sets neither O_CREAT nor O_TRUNC, so it passes this check, and smb2_set_stream_name_xattr() then creates the stream. On a Time Machine share, opening a missing AFP_AfpInfo stream also writes one. A user who can write a file at the filesystem level can therefore add streams to it through a read-only share. Do not create a stream or synthesize AFP_AfpInfo when the share is not writable. Existing streams still open normally, and a missing stream opened with FILE_OPEN still returns STATUS_OBJECT_NAME_NOT_FOUND.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.15, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <09139429fab3a5114c18d7c15fb161511d4d66c9, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <ece35b45ec17a462cc5947ad4fbc3450657aa55b | 09139429fab3a5114c18d7c15fb161511d4d66c9, ece35b45ec17a462cc5947ad4fbc3450657aa55b |
| linux-kernel: Kernel | >=5.15.0 <7.3.5 | 7.3.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket