CVE-2026-23346 is an arm64 Linux kernel vulnerability in the handling of ioremap_prot(). The issue arises because generic_access_phys(), the only non-generic caller noted for ioremap_prot(), passes a pgprot_t value derived from a user mapping of the target PFN. On arm64, pgprot_t carries all non-address PTE bits, including permission controls. As a result, ioremap_prot() could create a new mapping that preserves inappropriate user permission attributes instead of only the memory type. On systems with PAN enabled, the kernel can then fault when accessing that mapping, as shown by the crash path through __memcpy_fromio(), generic_access_phys(), and access_remote_vm(). The upstream fix changes arm64 ioremap_prot() to extract only the memory type from the user pgprot_t, asserts that the supplied mapping is a user mapping, and adds an arm64-specific ioremap() wrapper around __ioremap_prot() to avoid false positives for normal ioremap() users.
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.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.