Kernel code execution via use-after-free
Published Aug 24, 2021 · Updated Aug 3, 2024
Use-after-free in the Apple kernel in macOS, iOS and iPadOS, and watchOS allows local users to execute code with kernel privileges. The undisclosed kernel memory-management path accesses an object after its lifetime ends, allowing an application to reuse freed memory during kernel execution. Exploitation requires a locally run application; successful execution crosses the user-to-kernel boundary and grants kernel-level control.
Summary
What happened
Use-after-free in the Apple kernel in macOS, iOS and iPadOS, and watchOS allows local users to execute code with kernel privileges. The undisclosed kernel memory-management path accesses an object after its lifetime ends, allowing an application to reuse freed memory during kernel execution. Exploitation requires a locally run application; successful execution crosses the user-to-kernel boundary and grants kernel-level control.
The record
- CVE
- CVE-2021-30980
- Published
- Aug 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 24, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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.2
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