Kernel-state disclosure via insufficient log redaction
Published Oct 28, 2024 · Updated Apr 2, 2026
Information disclosure in the Kernel component of iOS, iPadOS, macOS, tvOS, visionOS, and watchOS allows local users to read kernel state. The Kernel writes private kernel data into log entries without sufficient redaction, making that data available to an app that can access those entries. Execution of a local app is required, and the documented impact is limited to disclosure of sensitive kernel state.
Summary
What happened
Information disclosure in the Kernel component of iOS, iPadOS, macOS, tvOS, visionOS, and watchOS allows local users to read kernel state. The Kernel writes private kernel data into log entries without sufficient redaction, making that data available to an app that can access those entries. Execution of a local app is required, and the documented impact is limited to disclosure of sensitive kernel state.
The record
- CVE
- CVE-2024-44239
- Published
- Oct 28, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-532, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 28, 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 <17.7.1
- Affected versionversion=0 <18.1
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.
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