{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93052 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-93052 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-93052 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93052/ (Markdown: https://insights.sbomify.com/CVE-2026-93052/index.md)","id":"CVE-2026-93052","markdown":"https://insights.sbomify.com/CVE-2026-93052/index.md","name":"CVE-2026-93052","record":{"aliases":["AZL-102750","BELL-CVE-2026-93052","DEBIAN-CVE-2026-93052","GHSA-8pr8-738w-j3vf","UBUNTU-CVE-2026-93052"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"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.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmisc: bcm-vk: Use acquire/release for msgq_inited\n\nbcm_vk_sync_msgq() fills the message queue information and then sets\nmsgq_inited. Readers call bcm_vk_drv_access_ok() before accessing the\nmessage queues and their cached queue information.\n\natomic_set()/atomic_read() do not order those accesses. A reader can see\nmsgq_inited set while still seeing stale queue information. Use release\nwhen publishing the initialized queues and acquire when checking the gate.\n\nKeep the clear in bcm_vk_blk_drv_access() as atomic_set(). It closes the\ngate and does not publish queue state to readers.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"misc: bcm-vk: Use acquire/release for msgq_inited","id":"CVE-2026-93052","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"speakup: keyhelp: guard letter_offsets possible out-of-range indexing","id":"CVE-2026-93053"},"packages":[],"prev":{"headline":"misc: ad525x_dpot: use driver core groups for sysfs files","id":"CVE-2026-93051"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"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.","url":"https://insights.sbomify.com/CVE-2026-93052/"}