CVE-2026-99748: ksmbd: revert fsids on durable reconnect and replay failure

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: revert fsids on durable reconnect and replay failure

On a durable handle reconnect or a request replay, smb2open() switches to the SMB user's fsids before calling ksmbdvfsgetattr(). If that call fails, the code jumps to errout2 and skips ksmbdrevertfsids() at errout1. The user's credentials then stay installed on the shared ksmbd worker. Later work on that worker, including other users' requests, runs with the first user's fsuid, fsgid and supplementary groups. ksmbdfreeworkstruct() also warns, because work->savedcred is still set.

Jump to errout1 instead. No path is held at this point, so skipping the pathput() at errout is correct.

Affected Software

5 affected componentsFixes available
linux/kernel>=6.6.32<6.7
6.7
linux/kernel>=6.9.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux<=6.12.107-1, <=6.12.117-1, <=7.3.4-1
6.1.176-16.1.192-27.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 6.7
  2. Upgrade

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

    Fixed in 7.3.5
  3. Upgrade

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

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed 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 is exposed to this issue?

Systems using the Linux kernel's ksmbd SMB server are exposed on the affected durable-handle reconnect and request-replay error paths. The risk is greatest where a shared ksmbd worker subsequently processes requests for different SMB users.

2

What must occur for the credential leak to be triggered?

An SMB durable handle reconnect or request replay must cause smb2_open() to switch to an SMB user's fsids, followed by a failure from ksmbd_vfs_getattr(). The failure path then leaves that user's fsuid, fsgid, and supplementary groups installed on the shared worker.

3

What is the security impact after the failure?

Later work handled by the same ksmbd worker, including requests from other users, can run under the first user's credentials. The affected path also leaves work->saved_cred set, which causes a warning when ksmbd_free_work_struct() runs.

4

How can administrators tell whether this condition has occurred?

A warning from ksmbd_free_work_struct() indicating that work->saved_cred remains set is an indicator of the affected failure path. The issue requires a ksmbd_vfs_getattr() failure during durable reconnect or replay processing.

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