Linux kernel heap out-of-bounds write in ksmbd Kerberos authentication
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 98422bdd4cb3ca4d08844046f6507d7ec2c2b8d8 · < 4722d06b2907585074252061b1024a696c1cfc23| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix heap out-of-bounds write in krb5_authenticate()
In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming Kerberos AP-REP token. However, when SMB2_SESSION_SETUP is processed as a non-first element of a compounded SMB2 request, the calculation omits work->next_smb2_rsp_hdr_off.
This causes out_len to overstate remaining buffer headroom by the cumulative size of prior responses in the compound chain. Consequently, the length check in ksmbd_krb5_authenticate() (*out_len <= resp->spnego_blob_len) passes erroneously, allowing memcpy() to write the AP-REP blob past the end of response_buf into adjacent kernel heap memory.
Fix this by subtracting work->next_smb2_rsp_hdr_off when computing out_len, ensuring it accurately reflects physical remaining buffer space.
From the CVE record · Linux
Linux kernel ksmbd miscalculates response-buffer space during Kerberos authentication when SMB2_SESSION_SETUP is not the first request in a compounded SMB2 request. A network attacker who can send such a request may cause the AP-REP token to be written beyond the buffer into adjacent kernel heap memory. The input does not specify whether authentication or user interaction is required.
Operators running Linux kernels with ksmbd should check their exposure; affected versions are not specified.