smb: client: reject overlapping data areas in SMB2 responses
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 53b7c271f06be4dd5cfc8c6ef552a8355c891a7f · < 8986c932905ea508d66da421eb2eb6e676ace1fe| No fix yet |
| Linux Linux | — | No fix yet |
In the Linux kernel, the following vulnerability has been resolved:
smb: client: reject overlapping data areas in SMB2 responses
Commit 53b7c271f06b ("smb: client: restrict implied bcc[0] exemption to responses without data area") restricted the implied bcc[0] length exception to responses without a data area. However, the overlap handling in __smb2_calc_size() clears data_length, which can make an invalid response appear to have no data area and so qualify for the exception.
Track data area overlap separately and reject such responses before applying the length compatibility exceptions.
From the CVE record · Linux
The Linux kernel SMB client can mishandle overlapping data areas in SMB2 responses, making an invalid response appear eligible for a length exception. A remote SMB server could send such a response to a client; the input does not specify authentication or user-interaction requirements.
Engineers running Linux systems that use the kernel SMB client should check their kernel versions; affected versions are not specified.