Kernel code execution via undisclosed DriverKit memory flaw
Published Dec 15, 2022 · Updated Apr 21, 2025
A DriverKit memory-safety flaw in affected Apple macOS releases allows local users to execute arbitrary code with kernel privileges. Apple identifies the DriverKit component and improper memory handling but has not disclosed the faulty operation or attacker-controlled input. A local app must run on Big Sur before 11.7.2, Monterey before 12.6.2, or Ventura 13.0 to reach the kernel-level impact.
Summary
What happened
A DriverKit memory-safety flaw in affected Apple macOS releases allows local users to execute arbitrary code with kernel privileges. Apple identifies the DriverKit component and improper memory handling but has not disclosed the faulty operation or attacker-controlled input. A local app must run on Big Sur before 11.7.2, Monterey before 12.6.2, or Ventura 13.0 to reach the kernel-level impact.
The record
- CVE
- CVE-2022-32942
- Published
- Dec 15, 2022
- Updated
- Apr 21, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-125, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2022CVE publishedPublication date reported by the CVE source.
- Apr 21, 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 <11.7
- Affected versionversion=unspecified <12.6
- Affected versionversion=unspecified <13.1
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.
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