Loading vulnerability…
CVE-2025-22097 is a memory-safety vulnerability in the Linux kernel DRM Virtual Kernel Mode Setting (VKMS) driver, introduced in Linux kernel 5.12. When VKMS driver initialization fails, its cleanup routine can access an uninitialized or previously freed default configuration pointer and can free that allocation a second time. The upstream correction defers initialization of the pointer until driver initialization has completed successfully. The flaw is both a use-after-free condition (CWE-416) and a potential double-free condition.
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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel DRM/VKMS use-after-free and double-free vulnerability on an initialization error path.
A Linux kernel DRM/VKMS use-after-free and double-free vulnerability triggered during initialization error handling.
Linux kernel DRM/VKMS initialization-error flaw that can result in use-after-free and double-free conditions.
A use-after-free and double-free vulnerability in the Linux kernel VKMS DRM driver's initialization error path.
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.