ksmbd: fix type confusion via race condition when using ipc_msg_send_request
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix type confusion via race condition when using ipc_msg_send_request
req->handle is allocated using ksmbd_acquire_id(&ipc_ida), based on ida_alloc. req->handle from ksmbd_ipc_login_request and FSCTL_PIPE_TRANSCEIVE ioctl can be same and it could lead to type confusion between messages, resulting in access to unexpected parts of memory after an incorrect delivery. ksmbd check type of ipc response but missing add continue to check next ipc reponse.
From the CVE record · Linux
A race condition in ksmbd IPC request handling can cause two different messages to share a handle. An incorrect response delivery can then cause type confusion and access to unexpected parts of memory. The input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Engineers running the Linux kernel with ksmbd should check their deployments; affected versions are not specified.