ksmbd: fix use-after-free in __smb2_lease_break_noti()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in __smb2_lease_break_noti()
Move tcp_transport free to ksmbd_conn_free. If ksmbd connection is referenced when ksmbd server thread terminates, It will not be freed, but conn->tcp_transport is freed. __smb2_lease_break_noti can be performed asynchronously when the connection is disconnected. __smb2_lease_break_noti calls ksmbd_conn_write, which can cause use-after-free when conn->ksmbd_transport is already freed.
From the CVE record · Linux
The Linux kernel’s ksmbd component has a use-after-free in asynchronous lease-break notifications. If a connection remains referenced after its server thread terminates and its transport is freed, a notification after disconnection can access the freed transport. The input does not specify authentication requirements or user interaction.
Engineers running Linux kernels with ksmbd should check whether their kernel is affected; affected versions are not specified.