Loading vulnerability…
A privilege escalation vulnerability affecting the Windows Kernel Streaming WOW Thunk Service Driver. The issue is identified by Microsoft as an elevation of privilege flaw in a kernel-associated Windows component. Specific technical details about the vulnerable code path, root cause, and exploitation mechanism are not currently available from the provided information.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (POC) exploit for CVE-2024-38144, targeting a Microsoft Windows kernel streaming (KS) device interface. The main file, 'CVE-2024-38144.c', is a C program that opens a handle to a specific device interface (TEE_INTERFACE), creates a pin on the device, and sends a malformed IOCTL_KS_ENABLE_EVENT request with an intentionally invalid output buffer length. This action is designed to trigger the vulnerability in the target device driver. The exploit demonstrates the ability to interact with the vulnerable interface and send crafted IOCTL requests, but does not include a weaponized or post-exploitation payload. The attack vector is local, requiring the attacker to execute code on the target Windows system. The only fingerprintable endpoint is the device path used to access the vulnerable interface. The repository also includes a brief README with acknowledgments.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.