zram: fix slot lock bit position on big-endian 64-bit
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:
zram: fix slot lock bit position on big-endian 64-bit
The slot lock is a bit operation on the whole __lock word, which flags and ac_time alias as two u32s. On little-endian the lock bit lands in the position ZRAM_ENTRY_LOCK reserves in flags, so the aliasing works out. On 64-bit big-endian it lands in ac_time instead: with ZRAM_TRACK_ENTRY_ACTIME enabled, storing the access time from mark_slot_accessed() or slot_free() wipes out the held lock bit, letting another CPU take the same slot lock; an access time value with that bit set makes the slot look locked forever.
Shift the lock bit into the flags half of the word on big-endian 64-bit.
From the CVE record · Linux
On 64-bit big-endian Linux systems with ZRAM_TRACK_ENTRY_ACTIME enabled, the zram slot lock bit can land in the access-time field instead of the flags field. An access-time update can clear a held lock, allowing another CPU to acquire the same slot lock, or can make a slot appear locked indefinitely. The input does not specify an attacker access requirement or user interaction.
Engineers running the Linux kernel on 64-bit big-endian systems with ZRAM_TRACK_ENTRY_ACTIME enabled should check their systems; affected versions are not specified.