CVE-2026-99747: ksmbd: fix NULL pointer dereference in session_user_name() and session_account_type()

Published Nov 20, 2026
·
Updated

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

ksmbd: fix NULL pointer dereference in sessionusername() and sessionaccounttype()

sessionusername() and sessionaccounttype() dereference session->user without checking for NULL. A session can be published and exposed via the procfs session interface before authentication completes, during which session->user is NULL:

showprocsession() -> sessionusername(sess) -> userguest(session->user) -> NULL->flags -> oops

Guard both functions by treating a NULL session->user as an explicit not-yet-authenticated state rather than dereferencing it.

Affected Software

4 affected componentsFixes available
linux/kernel>=7.2.8<7.3
7.3
linux/kernel>=7.3.0<7.3.5
7.3.5
debian/linux*
debian/linux<=7.3.4-1
6.1.176-16.1.192-26.12.107-16.12.117-17.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
  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 6.12.107-1Fixed in 6.12.117-1Fixed 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

Which systems are exposed to this issue?

Systems using the Linux kernel's ksmbd SMB server functionality are exposed when the procfs session interface can observe a session before authentication has completed. The vulnerable path is in procfs session reporting, not in an authenticated session.

2

What condition triggers the crash?

A ksmbd session must be published before authentication completes, leaving session->user as NULL, and the procfs session display path must call session_user_name() or session_account_type(). Those functions dereference the NULL user pointer, causing an oops.

3

How does the fix change handling of incomplete sessions?

The fix treats a NULL session->user as an explicit not-yet-authenticated state. This prevents session_user_name() and session_account_type() from dereferencing the pointer before authentication has assigned a user.

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