Kernel-memory write via insufficient bounds checks
Published Jan 10, 2024 · Updated Jun 20, 2025
Memory corruption in the AMD component in Apple macOS before 13.3 allows local users to write kernel memory or terminate the system. The component applies insufficient bounds checks during an undisclosed operation, allowing app-controlled access to exceed its intended memory boundary. Execution of a crafted local app with user interaction is required; successful exploitation corrupts kernel state or crashes the operating system.
Summary
What happened
Memory corruption in the AMD component in Apple macOS before 13.3 allows local users to write kernel memory or terminate the system. The component applies insufficient bounds checks during an undisclosed operation, allowing app-controlled access to exceed its intended memory boundary. Execution of a crafted local app with user interaction is required; successful exploitation corrupts kernel state or crashes the operating system.
The record
- CVE
- CVE-2023-32436
- Published
- Jan 10, 2024
- Updated
- Jun 20, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-119, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 10, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 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 <13.3
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