CVE-2026-93052: Linux kernel · misc: bcm-vk: Use acquire/release for msgq_inited
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f7a8f4cbc8cede0be55220367dc52b126e2d39e5 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f7a8f4cbc8cede0be55220367dc52b126e2d39e5, bab66a9e30e39a06f3463b19f8c704386dfd5268, a45d6dd3c11e921882a2e74c7c8710b975f2eaa7 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/bab66a9e30e39a06f3463b19f8c704386dfd5268 (opens in a new tab)
- git.kernel.org/stable/c/679cfada6868723ccf162ec3b78c7402ff2405bf (opens in a new tab)
- git.kernel.org/stable/c/f7a8f4cbc8cede0be55220367dc52b126e2d39e5 (opens in a new tab)
- git.kernel.org/stable/c/1df3926ed8771edf286ff753428b243f334e6041 (opens in a new tab)
- git.kernel.org/stable/c/a45d6dd3c11e921882a2e74c7c8710b975f2eaa7 (opens in a new tab)
- git.kernel.org/stable/c/4984277bc43f84d7506346a09b29af138246d54a (opens in a new tab)
- git.kernel.org/stable/c/61b101c6a150057b6d512421ed108aed16e822ea (opens in a new tab)