Kernel-state disclosure via improper synchronization
Published Dec 11, 2024 · Updated Apr 2, 2026
A kernel race condition in Apple iOS, iPadOS, macOS, tvOS, and watchOS allows local users to leak sensitive kernel state through an app. The Kernel component improperly synchronizes shared state, allowing concurrent access to expose it; Apple has not identified the affected function or data structure. Local code execution and winning a high-complexity race are required, and the documented consequence is disclosure only.
Summary
What happened
A kernel race condition in Apple iOS, iPadOS, macOS, tvOS, and watchOS allows local users to leak sensitive kernel state through an app. The Kernel component improperly synchronizes shared state, allowing concurrent access to expose it; Apple has not identified the affected function or data structure. Local code execution and winning a high-complexity race are required, and the documented consequence is disclosure only.
The record
- CVE
- CVE-2024-54510
- Published
- Dec 11, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-362, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record 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=0 <18.2
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