Loading vulnerability…
A flaw in the Linux kernel Qualcomm command database (cmd-db) driver mapped cmd-db shared memory as write-back cacheable memory. The region is protected against writes by Qualcomm's XPU, but clean cache eviction may be falsely detected as a write, causing a secure interrupt and an endless loop in TrustZone. The issue is exposed when the second-stage translation does not independently map the region as non-cacheable, such as under hypervisors that lack Qualcomm-specific mappings. The fix changes the cmd-db mapping from write-back to write-combining memory.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel Qualcomm command-database shared-memory mapping issue.
Linux kernel Qualcomm command database shared-memory mapping flaw.
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.