Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93052

misc: bcm-vk: Use acquire/release for msgq_inited

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 111d746bb4767ad476f80fe49067e3df3d9a9375 – < bab66a9e30e39a06f3463b19f8c704386dfd5268
    • affected 111d746bb4767ad476f80fe49067e3df3d9a9375 – < 679cfada6868723ccf162ec3b78c7402ff2405bf
    • affected 111d746bb4767ad476f80fe49067e3df3d9a9375 – < f7a8f4cbc8cede0be55220367dc52b126e2d39e5
    • affected 111d746bb4767ad476f80fe49067e3df3d9a9375 – < 1df3926ed8771edf286ff753428b243f334e6041
    • affected 111d746bb4767ad476f80fe49067e3df3d9a9375 – < a45d6dd3c11e921882a2e74c7c8710b975f2eaa7
    • affected 111d746bb4767ad476f80fe49067e3df3d9a9375 – < 4984277bc43f84d7506346a09b29af138246d54a
    • affected 111d746bb4767ad476f80fe49067e3df3d9a9375 – < 61b101c6a150057b6d512421ed108aed16e822ea
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93052 badge
[![CVE-2026-93052](https://cveledger.app/badge/CVE-2026-93052.svg)](https://cveledger.app/cve/CVE-2026-93052)

Record last updated .