Bug 2577790 (CVE-2026-99749) - CVE-2026-99749 kernel: kernel: ksmbd: read-only share bypass via named stream creation
Summary: CVE-2026-99749 kernel: kernel: ksmbd: read-only share bypass via named stream...
Keywords:
Status: NEW
Alias: CVE-2026-99749
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 06:14 UTC by OSIDB Bzimport
Modified: 2026-11-20 11:12 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 06:14:00 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.