# 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.

- **Severity:** Not scored
- **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:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102750, BELL-CVE-2026-93052, DEBIAN-CVE-2026-93052, GHSA-8pr8-738w-j3vf, UBUNTU-CVE-2026-93052

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93052 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-93052 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93052/ (Markdown: https://insights.sbomify.com/CVE-2026-93052/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93052
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93052
- OSV: https://osv.dev/vulnerability/CVE-2026-93052

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93052/
Summaries are generated and may contain mistakes; the official description above is the record.