Kernel memory-protection bypass via RTKit out-of-bounds write
Published Mar 5, 2024 · Updated Apr 2, 2026
Memory corruption in RTKit across Apple operating systems allows local users with kernel read and write capability to bypass memory protections. RTKit insufficiently validates data used for a memory write, permitting an out-of-bounds write that corrupts protected kernel state. Exploitation requires prior arbitrary kernel read and write capability, so the flaw is a follow-on bypass rather than initial access; exploitation has been reported.
Summary
What happened
Memory corruption in RTKit across Apple operating systems allows local users with kernel read and write capability to bypass memory protections. RTKit insufficiently validates data used for a memory write, permitting an out-of-bounds write that corrupts protected kernel state. Exploitation requires prior arbitrary kernel read and write capability, so the flaw is a follow-on bypass rather than initial access; exploitation has been reported.
The record
- CVE
- CVE-2024-23296
- Published
- Mar 5, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 5, 2024CVE publishedPublication date reported by the CVE source.
- Mar 6, 2024Exploitation reportedCISA Known Exploited Vulnerabilities catalog entry
- 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.4
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.
Reported exploitation
- Apple reported exploitationreported exploitation
- CISA Known Exploited Vulnerabilities catalog entryknown exploited catalog
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