smb: client: split cached_fid bitfields to avoid shared-byte RMW races
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ebe98f1447bbccf8228335c62d86af02a0ed23f7 · < ec306600d5ba7148c9dbf8f5a8f1f5c1a044a241| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
smb: client: split cached_fid bitfields to avoid shared-byte RMW races
is_open, has_lease and on_list are stored in the same bitfield byte in struct cached_fid but are updated in different code paths that may run concurrently. Bitfield assignments generate byte read–modify–write operations (e.g. `orb $mask, addr` on x86_64), so updating one flag can restore stale values of the others.
A possible interleaving is: CPU1: load old byte (has_lease=1, on_list=1) CPU2: clear both flags (store 0) CPU1: RMW store (old | IS_OPEN) -> reintroduces cleared bits
To avoid this class of races, convert these flags to separate bool fields.
From the CVE record · Linux
The Linux kernel SMB client stores cached_fid flags in a shared bitfield byte that concurrent code paths can update, allowing an update to restore flags that another path cleared. The input does not establish what an attacker could achieve or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with the affected SMB client should check their versions against the vendor advisory; affected versions are not specified.