Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Kernel arbitrary code execution in Apple iOS/iPadOS/macOS

IdentifiersCVE-2023-38424CWE-787

Apple states that CVE-2023-38424 was addressed with improved memory handling and is fixed in iOS 16.6, iPadOS 16.6, and macOS Ventura 13.5. The issue could allow an application to execute arbitrary code with kernel privileges. The provided content does not identify the specific vulnerable component or function, but Apple’s description indicates a memory-safety flaw in kernel-reachable code that could be triggered by a local app to achieve kernel-level code execution.

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 may allow a local application to execute arbitrary code in the kernel context. This would give the attacker kernel privileges, enabling full compromise of the affected device, including bypass of application sandboxing, elevation to the highest local privilege level, access to sensitive data, and the ability to alter system behavior or establish persistent control.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting installation and execution of untrusted or unnecessary applications, enforcing application allowlisting where available, and restricting local code execution paths on managed devices. Because the issue is exploitable by an app and results in kernel-level code execution, there is no complete mitigation short of applying Apple's security updates.

Remediation

Patch, then assume compromise.

Update affected devices to iOS 16.6, iPadOS 16.6, or macOS Ventura 13.5 or later, as Apple indicates the issue is fixed in those releases. Apple states the vulnerability was addressed through improved memory handling.
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

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 evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

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 activity

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