Read-only memory modification via Kernel race
Published Dec 11, 2024 · Updated Apr 2, 2026
A Kernel race condition in affected Apple operating systems allows attackers to create writable mappings of read-only memory. Apple has not disclosed the Kernel code path or validation failure that lets a raced mapping retain write access. Successful exploitation requires winning the race and permits modification of memory intended to remain read-only; no broader impact is documented.
Summary
What happened
A Kernel race condition in affected Apple operating systems allows attackers to create writable mappings of read-only memory. Apple has not disclosed the Kernel code path or validation failure that lets a raced mapping retain write access. Successful exploitation requires winning the race and permits modification of memory intended to remain read-only; no broader impact is documented.
The record
- CVE
- CVE-2024-54494
- Published
- Dec 11, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-362
- Attack vector
- network
- 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?
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