Kernel-memory writes or unexpected system termination
Published Aug 24, 2022 · Updated May 29, 2025
An out-of-bounds write in the Wi-Fi component of Apple macOS before 12.5 and tvOS before 15.6 allows local users to write kernel memory. Apple has not published the affected function, the unchecked value, or the precise operation that writes beyond its intended bounds. Execution requires a locally launched app and user interaction; successful exploitation can corrupt kernel memory or terminate the system.
Summary
What happened
An out-of-bounds write in the Wi-Fi component of Apple macOS before 12.5 and tvOS before 15.6 allows local users to write kernel memory. Apple has not published the affected function, the unchecked value, or the precise operation that writes beyond its intended bounds. Execution requires a locally launched app and user interaction; successful exploitation can corrupt kernel memory or terminate the system.
The record
- CVE
- CVE-2022-32837
- Published
- Aug 24, 2022
- Updated
- May 29, 2025
- Vendor
- Apple
- Product
- tvOS
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2022CVE publishedPublication date reported by the CVE source.
- May 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 <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