Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2023-41974: IOSurfaceRoot use-after-free kernel privilege escalation in iOS and iPadOS

Published Jan 10, 2024 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS2.0%81st percentile
CISA KEVYesAdded Mar 5, 2026
In the wildActivePer CISA KEV
Vendor
Apple
IdentifiersCVE-2023-41974CWE-416 · Use After Free

CVE-2023-41974 is a kernel use-after-free vulnerability in iOS and iPadOS, reported in the Kernel component and associated in public reporting with IOSurfaceRoot. The flaw stems from improper object lifetime handling that can lead to memory corruption after a freed object is reused. Apple states the issue was addressed through improved memory management. Successful exploitation can allow a malicious application to execute arbitrary code with kernel privileges. Public reporting also describes the vulnerability as a kernel privilege-escalation component used in the Coruna exploit chain.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation enables arbitrary code execution in kernel context. This can give an attacker full control over the affected device, including bypass of application sandbox boundaries, elevation from app-level execution to root-equivalent kernel privileges, access to sensitive system and user data, modification of security-relevant state, and deployment of follow-on payloads or implants. In observed exploit-chain reporting, the vulnerability served as the kernel stage following initial code execution, enabling deeper compromise of the operating system.

Mitigation

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

Where immediate patching is not possible, reduce exposure by limiting installation and execution of untrusted applications, enforcing rapid update policies for Apple devices, and enabling Lockdown Mode for users at elevated risk, as reporting indicates the broader Coruna chain avoids execution on devices using Lockdown Mode. Additional defensive measures include mobile device management controls, application allowlisting where feasible, and monitoring for signs of post-exploitation on high-value devices. Mitigations are temporary and do not replace installing the vendor patch.

Remediation

Patch, then assume compromise.

Apply Apple security updates that fix CVE-2023-41974. The issue is fixed in iOS 17 and iPadOS 17, and was later backported to iOS 15.8.7 and iPadOS 15.8.7 for older supported devices. Organizations should ensure affected iPhones and iPads are updated to a version containing the patch, prioritizing exposed or high-risk users and any legacy devices still running vulnerable releases.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
SolariumThis standalone Xcode command-line project is a work-in-progress Swift reimplementation of CVE-2023-41974. It contains seven Swift source files, a README, a .gitignore, and six Xcode project/workspace metadata files. It is exploit code rather than a detection script, but provides exploitation primitives rather than a final post-exploitation payload. main.swift first calls allocatePPLpages(), initializes eSocket(count: 2048), and constructs a Translation object. common.swift performs sparse memory allocation and touching at 32 MiB intervals, then deallocates those mappings, apparently to influence page-table allocation. The helper's name and log messages do not establish a standalone PPL bypass. freePages.swift contains the Landa primitive and page-reclamation management. Visible code repeatedly calls mlock, runs another mlock operation in a synchronized thread around vm_copy, and deallocates a mapping. It subsequently uses patterned page copies and scans to identify reclaimed pages accessible through the retained mapping. The allocation loop permits up to 400,000 16 KiB pages, creating substantial resource pressure. Part of this file is truncated, so the exact initial corruption sequence cannot be independently reconstructed from the supplied excerpt. eSocket.swift sprays ICMPv6 datagram sockets in batches of 500, with up to ten batches. It identifies socket control blocks in reclaimed memory by their IPv6 hop-limit marker and verifies candidates by changing that option. It then overwrites the selected control block's ICMPv6-filter pointer to direct getsockopt and setsockopt at chosen kernel addresses, restoring the original pointer after each operation. The public API offers 32-byte reads/writes and 8-byte/4-byte read wrappers; the smaller reads still perform an underlying 32-byte read. A Mach-O-header scan locates the kernel base and derives the KASLR slide. VMSA.swift caches physical-to-virtual mappings, translation constants, and the L1 table, then walks ARM64 translation tables for kernel virtual-to-physical conversion and address validation. koffset.swift supplies build-specific kernel symbol addresses; kstruct.swift supplies extensive kernel structure layouts. These hardcoded assumptions constrain portability. No remote address, listener, command-and-control endpoint, exfiltration destination, or packet-transmission routine is visible. The sockets are local kernel-object manipulation tools, not evidence of remote exploitation. External URLs are documentation and build-dependency references. Potential reliability concerns include forced unwraps, an unbounded backward kernel-base scan, and extra removeLast() calls after popLast() in socket matching that can discard descriptors or trap on an empty array. Kernel crashes or resource exhaustion are plausible failure outcomes. No evidence in the supplied content indicates a fake exploit. Several files are truncated, and execution or successful exploitation was not verified. The original repository URL, Git reference, archive path, and archive size were not supplied; empty strings and zero represent unavailable repository metadata.kienhho · Disclosed Nov 7, 2026 · swift · localPoC
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
FAQ

Frequently asked questions

Is CVE-2023-41974 exploited in the wild?
Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 5, 2026.
Is there a public exploit for CVE-2023-41974?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2023-41974, the earliest disclosed Nov 7, 2026.
Is there a patch for CVE-2023-41974?
Apply Apple security updates that fix CVE-2023-41974. The issue is fixed in iOS 17 and iPadOS 17, and was later backported to iOS 15.8.7 and iPadOS 15.8.7 for older supported devices.
What products are affected by CVE-2023-41974?
Apple Ipados and Apple Iphone Os.
How severe is CVE-2023-41974?
CVE-2023-41974 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 2.0% (81st percentile) as of Sep 25, 2026.
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence17Every report linking this CVE to a named adversary.
Associated malware25Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity17Community discussion across Reddit, Mastodon, and other social sources.