Kernel code execution via insufficient graphics-driver locking
Published Aug 24, 2022 · Updated May 29, 2025
Memory corruption in the Intel Graphics Driver in Apple macOS allows local users to execute arbitrary code with kernel privileges. The driver performs insufficient locking around memory operations, allowing corruption; Apple has not identified the affected function or object. Execution requires a user to run a local app that reaches the driver, after which attacker-controlled code runs with kernel privileges.
Summary
What happened
Memory corruption in the Intel Graphics Driver in Apple macOS allows local users to execute arbitrary code with kernel privileges. The driver performs insufficient locking around memory operations, allowing corruption; Apple has not identified the affected function or object. Execution requires a user to run a local app that reaches the driver, after which attacker-controlled code runs with kernel privileges.
The record
- CVE
- CVE-2022-32811
- Published
- Aug 24, 2022
- Updated
- May 29, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-667, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2022CVE publishedPublication date reported by the CVE source.
- May 29, 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.6
- Affected versionversion=unspecified <12.5
- Affected versionversion=unspecified <2022
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