Kernel code execution via unsafe memory handling
Published Jan 10, 2024 · Updated Jun 20, 2025
Memory corruption in Apple Neural Engine in Apple macOS before 13 allows local users to execute arbitrary code with kernel privileges. The component handles app-supplied data with inadequate memory management, but Apple has not disclosed the affected routine or memory operation. Execution of a malicious local app and user interaction are required; successful exploitation runs attacker-controlled code with kernel privileges.
Summary
What happened
Memory corruption in Apple Neural Engine in Apple macOS before 13 allows local users to execute arbitrary code with kernel privileges. The component handles app-supplied data with inadequate memory management, but Apple has not disclosed the affected routine or memory operation. Execution of a malicious local app and user interaction are required; successful exploitation runs attacker-controlled code with kernel privileges.
The record
- CVE
- CVE-2022-47965
- Published
- Jan 10, 2024
- Updated
- Jun 20, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-119, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <13
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo