Loading vulnerability…
A buffer overrun vulnerability exists in multiple Qualcomm Snapdragon chipsets during listener modified response processing. The vulnerability is due to a lack of buffer size verification when updating the message buffer with physical address information. This flaw can be triggered when the listener processes a modified response, potentially allowing an attacker to overwrite memory beyond the intended buffer boundaries.
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-2019-14041, a race condition vulnerability in the QSEECOM kernel driver on Qualcomm-based Android devices. The main exploit code is in 'jni/qseecom_race.c', which allocates ION memory via /dev/ion, registers a listener with /dev/qseecom, and attempts to trigger a race condition by rapidly issuing ioctl calls from multiple threads. The exploit is designed to be built with the Android NDK and run on a device where /dev/qseecom is accessible. If successful, it causes a kernel panic, demonstrating the vulnerability. The repository also includes relevant kernel header files (ion.h, msm_ion.h, qseecom.h) and a Makefile for building the PoC. The exploit is local (requires code execution on the device) and does not provide privilege escalation or a shell, but demonstrates denial-of-service capability by crashing the kernel.
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.