smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b24df3e30cbf48255db866720fb71f14bf9d2f39 · < 96c436e4b010711452b2872558938f4ef276492a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs
Fix several related bounds checking and pointer lifecycle issues in receive_encrypted_standard()'s handling of compound encrypted frames:
- Clear next_buffer after assigning it to server->bigbuf. A stale next_buffer pointer can lead to a use-after-free on subsequent error paths. - Update pdu_length to the decrypted plaintext size (buf_size). Using the pre-decryption length allows NextCommand to point into stale ciphertext residue. - Reject next_cmd values smaller than MID_HEADER_SIZE(server). - Fix an integer overflow in the upper bound check by verifying pdu_length - next_cmd < MID_HEADER_SIZE(server), ensuring the trailing slice is large enough for a header.
From the CVE record · Linux
The Linux kernel SMB client has pointer-lifecycle and bounds-checking flaws when handling compound encrypted frames. They can lead to a use-after-free or invalid NextCommand bounds; the input does not specify attacker access, authentication requirements, or user interaction.
Engineers running Linux kernels with the SMB client should check their versions; affected versions are not specified.