CVE-2024-51324: Arbitrary Process Termination in Baidu Antivirus BdApiUtil Driver
CVE-2024-51324 is an improper privilege management vulnerability in the BdApiUtil kernel driver associated with Baidu Antivirus v5.2.3.116083. It allows a local attacker to terminate arbitrary processes, including protected endpoint security processes, by abusing privileged driver functionality. Attackers have exploited the vulnerability through Bring Your Own Vulnerable Driver (BYOVD) techniques in DeadLock and GOLD SALEM ransomware operations. A related driver process-termination interface accepts IOCTL 0x800024B4 with a four-byte process identifier and reaches ZwTerminateProcess; attribution of separately analyzed driver version 4.6.1.65082 to this CVE remains qualified because its version differs from the identified antivirus product version.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Exploitation can disrupt applications and services and disable antivirus or endpoint detection and response processes. Terminating security agents impairs monitoring and prevention, facilitating subsequent malicious activity, including ransomware deployment. The demonstrated primitive is privileged process termination, not arbitrary kernel code execution.
Mitigation
If you can’t patch tonight, do this now.
Apply compatible vulnerable-driver controls, including Microsoft's vulnerable-driver blocklist and explicit WDAC or App Control policies targeting the affected driver. Enable the Microsoft Defender ASR rule for abused vulnerable signed drivers and Core Isolation Memory Integrity where supported and compatible. Restrict driver installation and loading to authorized administrators, inventory existing vulnerable drivers, and monitor unexpected driver-service creation followed by termination of security processes.
Remediation
Patch, then assume compromise.
A vendor-confirmed fixed version or patch is currently not available in the supplied information. Remove the affected driver from systems where it is unnecessary, and obtain vendor confirmation of a corrected release before retaining or redeploying it.
Exploits
3 exploits validated by Mallory's analysis.
Frequently asked questions
- Is CVE-2024-51324 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2024-51324?
- Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2024-51324, the earliest disclosed Mar 25, 2026.
- Is there a patch for CVE-2024-51324?
- A vendor-confirmed fixed version or patch is currently not available in the supplied information. Remove the affected driver from systems where it is unnecessary, and obtain vendor confirmation of a corrected release before retaining or redeploying it.
- How severe is CVE-2024-51324?
- CVE-2024-51324 has a CVSS v3.1 score of 3.8 (Low) and an EPSS score of 0.48% (42nd percentile) as of Oct 16, 2026.
Recent activity
25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.