Kernel code execution via memory state corruption
Published May 8, 2023 · Updated Jan 29, 2025
Memory corruption in Apple macOS before 13.3 and Studio Display firmware before 16.4 allows local users to execute kernel code. Apple has not disclosed the affected component or the invalid state transition that corrupts memory. Exploitation requires a user to run a crafted local app, after which code executes with kernel privileges on the affected Mac or display firmware.
Summary
What happened
Memory corruption in Apple macOS before 13.3 and Studio Display firmware before 16.4 allows local users to execute kernel code. Apple has not disclosed the affected component or the invalid state transition that corrupts memory. Exploitation requires a user to run a crafted local app, after which code executes with kernel privileges on the affected Mac or display firmware.
The record
- CVE
- CVE-2023-27965
- Published
- May 8, 2023
- Updated
- Jan 29, 2025
- Vendor
- Apple
- Product
- Studio Display Firmware Update
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 8, 2023CVE publishedPublication date reported by the CVE source.
- Jan 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 <16.4
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