Kernel code execution via undisclosed memory mishandling
Published Sep 23, 2022 · Updated May 22, 2025
Memory corruption in the Apple Kernel allows local users controlling a root-privileged app to execute arbitrary code with kernel privileges. Apple identifies the affected locus only as Kernel and states that improved memory handling addressed the issue, leaving the erroneous memory operation undisclosed. Exploitation requires user interaction to run a root-privileged app; successful exploitation crosses into kernel execution with full system impact.
Summary
What happened
Memory corruption in the Apple Kernel allows local users controlling a root-privileged app to execute arbitrary code with kernel privileges. Apple identifies the affected locus only as Kernel and states that improved memory handling addressed the issue, leaving the erroneous memory operation undisclosed. Exploitation requires user interaction to run a root-privileged app; successful exploitation crosses into kernel execution with full system impact.
The record
- CVE
- CVE-2022-32815
- Published
- Sep 23, 2022
- Updated
- May 22, 2025
- Vendor
- Apple
- Product
- tvOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
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.
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