Kernel-memory disclosure via GPU bounds-check failures
Published Aug 24, 2022 · Updated May 30, 2025
Out-of-bounds writes in Apple GPU Drivers in macOS before 12.5, tvOS before 15.6, and watchOS before 8.7 allow local users to read kernel memory. The drivers write beyond one or more undisclosed buffers because bounds checks do not adequately constrain app-supplied GPU input. Local app execution is required, and Apple reports kernel-memory disclosure without a corresponding integrity or availability impact.
Summary
What happened
Out-of-bounds writes in Apple GPU Drivers in macOS before 12.5, tvOS before 15.6, and watchOS before 8.7 allow local users to read kernel memory. The drivers write beyond one or more undisclosed buffers because bounds checks do not adequately constrain app-supplied GPU input. Local app execution is required, and Apple reports kernel-memory disclosure without a corresponding integrity or availability impact.
The record
- CVE
- CVE-2022-32793
- Published
- Aug 24, 2022
- Updated
- May 30, 2025
- Vendor
- Apple
- Product
- tvOS
- Classifications
- CWE-787, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 24, 2022CVE publishedPublication date reported by the CVE source.
- May 30, 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 <15.6
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