CVE-2026-99749: ksmbd: enforce the read-only share flag when creating a stream

Published Nov 20, 2026
·
Updated

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, smb2open() rejects opens that would create or truncate a file. Creating a named stream on an existing file with streamsxattr sets neither OCREAT nor OTRUNC, so it passes this check, and smb2setstreamnamexattr() then creates the stream. On a Time Machine share, opening a missing AFPAfpInfo 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 AFPAfpInfo when the share is not writable. Existing streams still open normally, and a missing stream opened with FILEOPEN still returns STATUSOBJECTNAMENOTFOUND.

Affected Software

5 affected componentsFixes available
linux/kernel>=5.15.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs filesystem-level permission to write the target file and access to it through a ksmbd read-only share. The issue affects attempts to add named streams to an existing file, including the AFP_AfpInfo stream behavior on Time Machine shares.

2

Are existing named streams blocked on a read-only share?

No. Existing streams continue to open normally. The fix prevents creating a missing stream or synthesizing AFP_AfpInfo when the share is not writable.

3

What behavior should indicate the fix is in effect?

Opening a missing stream with FILE_OPEN should return STATUS_OBJECT_NAME_NOT_FOUND. A read-only share should not create a named stream or write a missing AFP_AfpInfo stream.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203