Dell DBUtilDrv2.sys, a utility driver used by Dell update tooling for PC drivers, BIOS, and firmware, is affected by an insufficient access control vulnerability in versions 2.5 and 2.6. The flaw allows a local authenticated user to interact with the kernel driver in a way that should be more tightly restricted, enabling abuse of the driver's privileged functionality. The provided content specifically identifies DBUtilDrv2.sys as a vulnerable driver that has been used in Bring Your Own Vulnerable Driver (BYOVD) scenarios to modify kernel structures and tamper with kernel notification routines. The vulnerability is associated with local privilege escalation, denial of service, and information disclosure.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.