ksmbd: do not expire session on binding failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f5a544e3bab78142207e0242d22442db85ba1eff · < e0e5edc81b241c70355217de7e120c97c3429deb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: do not expire session on binding failure
When a multichannel session binding request fails (e.g. wrong password), the error path unconditionally sets sess->state = SMB2_SESSION_EXPIRED. However, during binding, sess points to the target session looked up via ksmbd_session_lookup_slowpath() -- which belongs to another connection's user. This allows a remote attacker to invalidate any active session by simply sending a binding request with a wrong password (DoS).
Fix this by skipping session expiration when the failed request was a binding attempt, since the session does not belong to the current connection. The reference taken by ksmbd_session_lookup_slowpath() is still correctly released via ksmbd_user_session_put().
From the CVE record · Linux
The Linux kernel's ksmbd component can expire another user's active session when a multichannel binding request fails. A remote attacker can invalidate an active session by sending a binding request with a wrong password; no valid password or user interaction is described.
Anyone running Linux with ksmbd should check whether their kernel is affected; affected versions were not specified.