smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3bc303c254335dbd7c7012cc1760b12f1d5514d3 · < 4165641d06ef44f3a31b77a28048b6c737e885e7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races
The invalidHandle, swapfile, oplock_break_cancelled, offload, and status_file_deleted fields are stored in the same bitfield byte in struct cifsFileInfo, but are updated in different code paths that may run simultaneously, and are protected by different locks. Since bitfield assignments generate byte-level read-modify-write operations, a modification to one flag can overwrite a concurrent modification to another flag.
To avoid these races, convert these flags from a bitfield to separate bool fields.
From the CVE record · Linux
The Linux kernel SMB client stores several file-state flags in one bitfield byte, where concurrent updates can overwrite each other. The input does not describe an attacker-controlled trigger or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the SMB client should check their affected versions; none are specified in the input.