Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Stack-based buffer overflow in Dell ControlVault3 securebio_identify

IdentifiersCVE-2025-24922CWE-121· Stack-based Buffer Overflow

CVE-2025-24922 is a stack-based buffer overflow in the securebio_identify functionality of Dell ControlVault3 firmware prior to 5.15.10.14 and Dell ControlVault3 Plus firmware prior to 6.2.26.36. According to the provided content, data from a property of a supplied cv_object is copied into a stack buffer named data2 without ensuring that the property length fits the destination buffer. A specially crafted malicious cv_object delivered through a ControlVault API call can therefore overflow the stack and corrupt adjacent memory. The issue affects the ControlVault firmware attack surface exposed through Dell/Broadcom host APIs and can be triggered by a local caller interacting with the device.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can lead to arbitrary code execution in the privileged ControlVault firmware context. The broader research context indicates that firmware code execution can be used to extract security-relevant key material from OTP-backed storage, tamper with firmware trust material, install modified firmware that remains accepted by the device, bypass fingerprint-based Windows Hello authentication, establish persistence that survives OS reinstallation, and potentially pivot back into the host to obtain elevated privileges through trusted biometric paths.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling unused ControlVault-related functionality and peripherals such as fingerprint, smart card, or NFC features where operationally feasible. Limit local access to systems, harden against post-compromise abuse, and monitor for abnormal loading of bcmbipdll.dll, unexpected access to the ControlVault device interface, and crashes in related services such as WinBioSvc and Broadcom/Dell ControlVault services. In higher-risk physical exposure scenarios, consider disabling fingerprint login and enabling chassis intrusion detection or Windows Enhanced Sign-in Security where supported.

Remediation

Patch, then assume compromise.

Update Dell ControlVault3 to version 5.15.10.14 or later and Dell ControlVault3 Plus to version 6.2.26.36 or later. Apply Dell-provided firmware updates through Windows Update or Dell support channels as applicable, and validate that affected systems are running remediated firmware versions.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.