Kernel code execution via AMD buffer overflow
Published Sep 26, 2023 · Updated Nov 4, 2025
Buffer overflow in the AMD component of Apple macOS before 14 allows local users to execute arbitrary code with kernel privileges. Apple identifies improper memory handling but has not published the specific AMD code locus, input, or unchecked operation that causes the overflow. Exploitation requires an app to reach the local kernel component and user interaction, after which the app gains kernel-level code execution.
Summary
What happened
Buffer overflow in the AMD component of Apple macOS before 14 allows local users to execute arbitrary code with kernel privileges. Apple identifies improper memory handling but has not published the specific AMD code locus, input, or unchecked operation that causes the overflow. Exploitation requires an app to reach the local kernel component and user interaction, after which the app gains kernel-level code execution.
The record
- CVE
- CVE-2023-32377
- Published
- Sep 26, 2023
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2023CVE publishedPublication date reported by the CVE source.
- Nov 4, 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 <14
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.
Weakness, pattern, technique
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