CVE-2026-93052

Unknown

Last modified

CVE-2026-93052 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 111d746bb4767ad476f80fe49067e3df3d9a9375, < bab66a9e30e39a06f3463b19f8c704386dfd5268; >= 111d746bb4767ad476f80fe49067e3df3d9a9375, < 679cfada6868723ccf162ec3b78c7402ff2405bf; >= 111d746bb4767ad476f80fe49067e3df3d9a9375, < f7a8f4cbc8cede0be55220367dc52b126e2d39e5; >= 111d746bb4767ad476f80fe49067e3df3d9a9375, < 1df3926ed8771edf286ff753428b243f334e6041; >= 111d746bb4767ad476f80fe49067e3df3d9a9375, < a45d6dd3c11e921882a2e74c7c8710b975f2eaa7; >= 111d746bb4767ad476f80fe49067e3df3d9a9375, < 4984277bc43f84d7506346a09b29af138246d54a; >= 111d746bb4767ad476f80fe49067e3df3d9a9375, < 61b101c6a150057b6d512421ed108aed16e822ea
LinuxLinux5.12

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-93052?
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.
How severe is CVE-2026-93052?
Severity scoring for CVE-2026-93052 is pending analysis.
How do I fix CVE-2026-93052?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-93052?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST