CVE-2025-31361: Broadcom BCM5820X · Use of Uninitialized Resource
Affects Broadcom BCM5820XSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 6.2.36.47 or 5.15.14.19 soon.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.2.36.47, 5.15.14.19
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 Broadcom BCM5820X to 6.2.36.47 or 5.15.14.19.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Broadcom BCM5820X | Affected
| Fixed in
|
AI-suggested
1. 2. Restrict local user privileges rigorously to minimize the number of users who can execute WinBioControlUnit API calls or access ControlVault driver interfaces. 3. Implement application whitelisting and endpoint detection and response (EDR) solutions to detect and block suspicious API calls or privilege escalation attempts related to ControlVault components. 4. Employ strict physical and logical access controls to prevent unauthorized local access to critical endpoints. 5. Conduct regular audits of local user accounts and privileges to identify and remediate excessive permissions. 6. Use multi-factor authentication and biometric security features carefully, ensuring they are updated and configured securely to reduce attack surface. 7. Prepare incident response plans to quickly contain and remediate privilege escalation incidents involving ControlVault vulnerabilities. 8. Consider network segmentation to limit lateral movement if a local compromise occurs. 9. Educate users and administrators about the risks of local privilege escalation and the importance of applying security updates promptly.
Description
A privilege escalation vulnerability exists in the ControlVault WBDI Driver WBIO_USH_ADD_RECORD functionality of Dell ControlVault3 prior to 5.15.14.19 and Dell ControlVault3 Plus prior to 6.2.36.47. A specially crafted WinBioControlUnit call can lead to privilege escalation. An attacker can issue an api call to trigger this vulnerability.