CVE-2026-74494: ksmbd: reject repeated SMB2 NEGOTIATE requests

Published Aug 15, 2026
·
Updated

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

ksmbd: reject repeated SMB2 NEGOTIATE requests

Unauthenticated client can send multiple successful SMB2 NEGOTIATE requests on one connection before SESSIONSETUP. While the connection is in KSMBDSESSNEEDSETUP, smb2handlenegotiate() accepts another SMB3.1.1 NEGOTIATE and overwrites conn->preauthinfo with a new allocation. Only the final allocation is freed when the connection is released, leaking one object for every additional successful request.

A repeated SMB2 NEGOTIATE after a dialect has been selected is a protocol violation. MS-SMB2 section 3.3.5.4 requires the server to disconnect without replying in this case. Set the connection exiting when rejecting the request, in addition to suppressing the response.

Reject SMB2 NEGOTIATE unless the connection is new or is waiting for the SMB2 NEGOTIATE that follows an SMB1 multi-protocol negotiate. Serialize both SMB1 and SMB2 negotiation paths under conn->srvmutex, since they update connection-wide dialect and negotiation state.

Move the locking contract to ksmbdsmbnegotiatecommon(), where the state and dialect are selected, and add ksmbdconnnew() for consistent state access.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Reject SMB2 NEGOTIATE requests when they are repeated for an existing connection state (after a dialect has already been selected), suppressing the response and setting the connection to exit in this case.

Event History

Aug 15, 2026
CVE Published
via MITRE·12:27 PM
Data Sourced
via MITRE·12:27 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-74494?

CVE-2026-74494 has a risk rating of 22, indicating a critical severity level.

2

How do I fix CVE-2026-74494?

To mitigate CVE-2026-74494, ensure you update your Linux kernel to the latest version where this vulnerability has been resolved.

3

What is the impact of CVE-2026-74494?

CVE-2026-74494 allows unauthenticated clients to send repeated SMB2 NEGOTIATE requests, potentially leading to denial of service.

4

Which versions of the Linux kernel are affected by CVE-2026-74494?

CVE-2026-74494 affects specific versions of the Linux kernel prior to the security update addressing this vulnerability.

5

Is CVE-2026-74494 exploitable remotely?

Yes, CVE-2026-74494 can be exploited by unauthenticated remote clients sending multiple SMB2 NEGOTIATE requests.

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