CVE-2025-21785 is an out-of-bounds write vulnerability in the Linux kernel ARM64 cacheinfo subsystem. The cache-information discovery and population loop bounded its cacheinfo-array index by cache level, but a single cache level may expose separate instruction-cache and data-cache leaves. Consequently, the loop could populate more array entries than its level-based accounting permitted. The correction advances the array index for every populated cache leaf rather than once per populated cache 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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel ARM64 cacheinfo out-of-bounds write vulnerability.
An out-of-bounds write vulnerability in the Linux kernel ARM64 cacheinfo array handling.
An out-of-bounds write vulnerability in the Linux kernel arm64 cacheinfo subsystem. Cache-information population could exceed the cacheinfo array bounds when cache levels expose separate data and instruction caches; the fix increments the index for every populated cache leaf rather than per populated level.
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.