Loading vulnerability…
CVE-2024-26947 is a Linux kernel ARM memory-management flaw in cache-flush handling for addresses that are reserved but not mapped into the kernel address space. Following a change to pfn_valid() semantics, such PFNs can be considered valid because a memory map is present. During a UIO remap operation, the ARM cache-maintenance path can then operate on a reserved, no-mapping folio and dereference an invalid kernel mapping. The fix checks whether the folio is marked reserved before performing the affected cache-flush operation.
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 ARM memory-flush flaw involving reserved folios for no-mapping addresses.
Linux kernel ARM memory-flush flaw involving reserved folios and no-mapping addresses.
Linux kernel ARM cache-flush flaw involving reserved folios for no-mapping addresses.
Linux kernel ARM memory-management flaw involving reserved folios and no-mapping addresses.
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.