misc: bcm-vk: Use acquire/release for msgq_inited
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 111d746bb4767ad476f80fe49067e3df3d9a9375 · < 4984277bc43f84d7506346a09b29af138246d54a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
misc: bcm-vk: Use acquire/release for msgq_inited
bcm_vk_sync_msgq() fills the message queue information and then sets msgq_inited. Readers call bcm_vk_drv_access_ok() before accessing the message queues and their cached queue information.
atomic_set()/atomic_read() do not order those accesses. A reader can see msgq_inited set while still seeing stale queue information. Use release when publishing the initialized queues and acquire when checking the gate.
Keep the clear in bcm_vk_blk_drv_access() as atomic_set(). It closes the gate and does not publish queue state to readers.
From the CVE record · Linux
The Linux kernel's bcm-vk driver can mark message queues initialized before readers see the updated queue information. A reader checking that initialization flag may then access stale queue information. The input does not specify attacker access requirements or whether user interaction is needed.
Engineers running Linux kernels with the bcm-vk driver should check their exposure; affected versions are not specified.