Kernel-memory disclosure via out-of-bounds read
Published Sep 23, 2022 · Updated May 22, 2025
Out-of-bounds read in the Apple kernel before macOS 12.5, tvOS 15.6, and watchOS 8.7 allows local users to disclose kernel memory. The kernel performs an out-of-bounds read because affected code lacks sufficient bounds checking, but Apple has not disclosed the function, buffer, or input structure. Execution of an app on the device is required, and the documented consequence is kernel-memory disclosure without reported modification or service interruption.
Summary
What happened
Out-of-bounds read in the Apple kernel before macOS 12.5, tvOS 15.6, and watchOS 8.7 allows local users to disclose kernel memory. The kernel performs an out-of-bounds read because affected code lacks sufficient bounds checking, but Apple has not disclosed the function, buffer, or input structure. Execution of an app on the device is required, and the documented consequence is kernel-memory disclosure without reported modification or service interruption.
The record
- CVE
- CVE-2022-32817
- Published
- Sep 23, 2022
- Updated
- May 22, 2025
- Vendor
- Apple
- Product
- tvOS
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 23, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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