Loading vulnerability…
A use-after-free vulnerability exists in the Qualcomm Secure Execution Environment (QSEE) implementation on multiple Snapdragon SoCs. The flaw is due to improper memory management, where memory is used after it has been freed, potentially allowing execution of arbitrary or unknown code. This affects a wide range of Snapdragon platforms across Auto, Compute, Consumer IoT, Industrial IoT, Mobile, Voice & Music, and Wearables product lines.
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 is a proof-of-concept (PoC) exploit for CVE-2019-14040, a use-after-free vulnerability in Qualcomm's QSEECom/ION kernel drivers affecting Android devices. The main exploit code is in 'jni/qseecom_uaf.c', which demonstrates how to trigger the vulnerability by manipulating ION memory buffers and interacting with the QSEECom device node. The exploit is designed to be built with the Android NDK and run on a vulnerable device with access to /dev/qseecom and /dev/ion. When executed, it causes a kernel panic, demonstrating a denial-of-service condition. The repository includes several header files for interacting with the relevant kernel interfaces and a Makefile for building the PoC. No remote or network attack vector is present; the exploit requires local code execution on the target device. The PoC does not provide privilege escalation or shell access, but serves as a demonstrative crash to aid in vulnerability verification and research.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.