Kernel code execution via unlocked graphics object
Published Apr 2, 2021 · Updated Aug 4, 2024
Memory corruption in the Intel Graphics Driver in Apple macOS before 11.1 allows local users to execute code with kernel privileges. The process_token_GenerateMipmaps path performs operations on a graphics object without proper locking, allowing its state to change between validation and use. Execution requires a local application and user interaction; successful exploitation elevates application code into kernel context.
Summary
What happened
Memory corruption in the Intel Graphics Driver in Apple macOS before 11.1 allows local users to execute code with kernel privileges. The process_token_GenerateMipmaps path performs operations on a graphics object without proper locking, allowing its state to change between validation and use. Execution requires a local application and user interaction; successful exploitation elevates application code into kernel context.
The record
- CVE
- CVE-2020-27907
- Published
- Apr 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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.0
- Affected versionversion=unspecified <11.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