CVE-2026-93052 misc: bcm-vk: Use acquire/release for msgq_inited
A race condition in the Linux kernel's bcm-vk driver allows readers to access stale message queue data, potentially causing information disclosure or system instability.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-93052?
CVE-2026-93052 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2026-93052?
How do I fix CVE-2026-93052?
Apply the vendor's patch.
Is CVE-2026-93052 being exploited?
There is no known exploitation of CVE-2026-93052 in the wild and no public exploit code.
Sources
Also known as AZL-102750, BELL-CVE-2026-93052, DEBIAN-CVE-2026-93052, GHSA-8pr8-738w-j3vf, UBUNTU-CVE-2026-93052.