Kernel code execution via use-after-free
Published Feb 27, 2023 · Updated Mar 11, 2025
Use-after-free in the kernel of Apple macOS before 13 allows local users to crash the system or execute code with kernel privileges. Apple identifies the kernel as the locus and a use-after-free as the wrong memory operation but does not disclose the affected function or object. Execution requires a locally launched app and user interaction; successful exploitation compromises the kernel, while failure can terminate the system.
Summary
What happened
Use-after-free in the kernel of Apple macOS before 13 allows local users to crash the system or execute code with kernel privileges. Apple identifies the kernel as the locus and a use-after-free as the wrong memory operation but does not disclose the affected function or object. Execution requires a locally launched app and user interaction; successful exploitation compromises the kernel, while failure can terminate the system.
The record
- CVE
- CVE-2022-46712
- Published
- Feb 27, 2023
- Updated
- Mar 11, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2023CVE publishedPublication date reported by the CVE source.
- Mar 11, 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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