Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Improper locking copy-on-write memory corruption in Apple XNU kernel

IdentifiersCVE-2025-43510CWE-667· Improper Locking

CVE-2025-43510 is an Apple kernel/XNU memory corruption vulnerability caused by improper locking during shared-memory copy-on-write handling. Apple describes the issue as a memory corruption bug fixed with improved lock state checking, where a malicious application may cause unexpected changes in memory shared between processes. Supporting reporting further characterizes it as a copy-on-write bug in the kernel that was used in the DarkSword exploit chain to escape from the GPU process and pivot execution into mediaplaybackd, where attackers reportedly built arbitrary function-call primitives. The issue affects multiple Apple platforms, including iOS, iPadOS, macOS, tvOS, visionOS, and watchOS, and was fixed in iOS/iPadOS 18.7.2 and 26.1, macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, and watchOS 26.1.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful exploitation can corrupt shared memory across process boundaries, leading to integrity violations in inter-process memory handling. In public reporting, the flaw was used as part of a chained exploit to achieve a sandbox escape from the GPU process into mediaplaybackd, enabling construction of attacker-controlled function-call primitives in a more privileged system service. On its own, the documented impact is unexpected modification of memory shared between processes; in an exploit chain, it can materially contribute to privilege escalation, sandbox escape, and progression toward full device compromise.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by preventing untrusted or malicious applications from executing on affected devices, restricting installation of non-essential apps, and applying heightened protections for high-risk users. Reporting on the associated DarkSword exploit chain indicates Lockdown Mode blocks the broader web-delivered chain on affected Apple devices, so enabling Lockdown Mode is a relevant interim mitigation for users at elevated risk. Standard compensating controls should also include rapid update enforcement, mobile device management restrictions, and monitoring for signs of exploitation or compromise.

Remediation

Patch, then assume compromise.

Apply Apple's security updates that address CVE-2025-43510: iOS 18.7.2 and iPadOS 18.7.2, iOS 26.1 and iPadOS 26.1, macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, and watchOS 26.1 or later. Because the vulnerability has been reported as actively exploited and added to CISA's KEV catalog, prioritize patching exposed and high-risk devices immediately.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType
AppleIpadosoperating_system
AppleIphone Osoperating_system
AppleMacosoperating_system
AppleTvosoperating_system
AppleVisionosoperating_system
AppleWatchosoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence17

Every observed campaign linking this CVE to a named adversary.

Associated malware34

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity13

Community discussion across Reddit, Mastodon, and other social sources.