CVE-2017-13218 concerns exposure of the ARM virtual count register CNTVCT_EL0 on affected Qualcomm Small Cell SoC, Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear platforms. According to the provided content, access to CNTVCT_EL0 gives local code access to a high-precision timer that can be used to improve the reliability of microarchitectural side-channel attacks. The issue does not itself grant code execution or elevated privileges; rather, it provides precise timing needed to observe subtle execution and cache effects and thereby facilitate attacks such as speculative-execution side channels on ARM processors. Google/Android describes the corresponding fix as reducing access to high-precision timers in the 2018-01-05 Security Patch Level.
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.
An Android-specific mitigation-related CVE covering timing mitigation for ARM processors in the 2018-01-05 Security Patch Level.
An Android vulnerability/update referenced as a mitigation measure that reduces access to high-precision timers to help limit side-channel attacks related to Spectre and Meltdown variants.
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.