Skip to main content
VulnerabilityPublished Updated

CVE-2026-93052: Linux kernel · misc: bcm-vk: Use acquire/release for msgq_inited

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f7a8f4cbc8cede0be55220367dc52b126e2d39e5 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

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

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 111d746bb4767ad476f80fe49067e3df3d9a9375, < f7a8f4cbc8cede0be55220367dc52b126e2d39e5
Fixed in
  • f7a8f4cbc8cede0be55220367dc52b126e2d39e5
LinuxLinuxAffected
  • ≥ 111d746bb4767ad476f80fe49067e3df3d9a9375, < bab66a9e30e39a06f3463b19f8c704386dfd5268
Fixed in
  • bab66a9e30e39a06f3463b19f8c704386dfd5268
LinuxLinuxAffected
  • ≥ 111d746bb4767ad476f80fe49067e3df3d9a9375, < a45d6dd3c11e921882a2e74c7c8710b975f2eaa7
Fixed in
  • a45d6dd3c11e921882a2e74c7c8710b975f2eaa7
LinuxLinuxAffected
  • ≥ 111d746bb4767ad476f80fe49067e3df3d9a9375, < 4984277bc43f84d7506346a09b29af138246d54a
Fixed in
  • 4984277bc43f84d7506346a09b29af138246d54a
LinuxLinuxAffected
  • ≥ 111d746bb4767ad476f80fe49067e3df3d9a9375, < 679cfada6868723ccf162ec3b78c7402ff2405bf
Fixed in
  • 679cfada6868723ccf162ec3b78c7402ff2405bf
LinuxLinuxAffected
  • ≥ 111d746bb4767ad476f80fe49067e3df3d9a9375, < 61b101c6a150057b6d512421ed108aed16e822ea
Fixed in
  • 61b101c6a150057b6d512421ed108aed16e822ea

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

Community reviews

Loading reviews…