ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea()
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 wrong next length validation of ea buffer in smb2_set_ea()
There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using ->NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea.
From the CVE record · Linux
The Linux kernel's ksmbd component incorrectly validates the length of extended-attribute buffers in an SMB2 FILE_FULL_EA_INFORMATION request. A client can send a request that causes ksmbd to access the next buffer without first validating its length; the input does not specify whether authentication is required or what further impact results.
Engineers running Linux kernels with ksmbd should check their installations; affected versions are not specified.