The mdp_lut_hw_update function in drivers/video/msm/mdp.c in the MDP display driver for Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices, fails to validate user-supplied start and length values in an ioctl call. This lack of input validation allows a local attacker to supply crafted values, potentially leading to privilege escalation via arbitrary memory access or modification.
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-2014-4323, targeting a vulnerability in the MSM framebuffer driver on Android devices. The main exploit code is in 'jni/pwn.c', which is compiled via the provided Android.mk build script. The exploit works by leaking kernel addresses from debugfs, manipulating the framebuffer device via ioctl calls, and setting up a trampoline to execute a kernel payload. The payload escalates privileges to root by calling commit_creds(prepare_kernel_cred(0)), then spawns a root shell. The exploit requires local access to the device and the presence of specific device files and kernel debugfs entries. The repository contains minimal documentation and is structured for use as a PoC for researchers or security professionals.
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.