Privilege escalation via Arm TLBI completion ordering flaw
CVE-2025-10263 is a critical Arm CPU erratum affecting multiple Arm C1, Neoverse, and Cortex cores. The issue arises from a timing/ordering condition during memory permission changes in which completion of certain memory accesses is not guaranteed by completion of a TLB invalidation (TLBI) and the associated synchronization barrier. As described by Arm and Xen, a broadcast TLBI on one processing element can complete before an affected store on another processing element has been globally observed under specific micro-architectural conditions. This can result in a write completing after page table or translation permissions have been changed to forbid writes to that location. In practice, software may still write to a previously writable location after the page tables or Stage 2 translation have been updated to revoke write access, potentially allowing writes to memory owned by a higher exception level. Xen notes the flaw may bypass Stage 1 translation, Stage 2 translation, or GPT protection, and does not affect reads.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
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.