CVE 8.8 HIGH

ksmbd: scope conn->binding slowpath to bound sessions only_CVE-2026-52911

8.8 / 10
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Description

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

ksmbd: scope conn->binding slowpath to bound sessions only

When the binding SESSION_SETUP sets conn->binding = true, the flag stays
set after the call so that the global session lookup in
ksmbd_session_lookup_all() can find the session, which was not added to
conn->sessions. Because the flag is connection-wide, the global lookup
path will also resolve any other session by id if asked.

Tighten the global lookup so that the returned session must have this
connection registered in its channel xarray (sess->ksmbd_chann_list).
The channel entry is installed by the existing binding_session path in
ntlm_authenticate()/krb5_authenticate() when a SESSION_SETUP completes
successfully, so this condition is a strict equivalent of "this
connection has been accepted as a channel of this session". Connections
that have not bound to a given session cannot reach it via the global
table.

The existing conn->binding gate for entering the slowpath is preserved
so that non-binding connections keep the fast-path-only behavior, and
the session->state check is unchanged.

Basic Information

ID CVE-2026-52911
Source Linux
Published Jun 21, 2026 at 06:18
Modified Jun 28, 2026 at 06:36

Affected Product

Vendor Linux
Product Linux
Version f5a544e3bab78142207e0242d22442db85ba1eff
Affected Versions Linux Linux f5a544e3bab78142207e0242d22442db85ba1eff
Linux Linux f5a544e3bab78142207e0242d22442db85ba1eff
Linux Linux f5a544e3bab78142207e0242d22442db85ba1eff
Linux Linux f5a544e3bab78142207e0242d22442db85ba1eff
Linux Linux f5a544e3bab78142207e0242d22442db85ba1eff
Linux Linux f5a544e3bab78142207e0242d22442db85ba1eff
Linux Linux f5a544e3bab78142207e0242d22442db85ba1eff
Linux Linux 5.15

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.