A memory corruption issue was addressed with improved validation.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 16.7.6, 17.4, 12.7.4, 13.6.5, 14.4, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apple's iOS, iPadOS, macOS, tvOS, visionOS, and watchOS are affected. An attacker who already has the ability to read and write kernel memory could use this flaw to get around the operating system's kernel memory protections.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A memory corruption issue was addressed with improved validation. This issue is fixed in iOS 16.7.6 and iPadOS 16.7.6, iOS 17.4 and iPadOS 17.4, macOS Monterey 12.7.4, macOS Sonoma 14.4, macOS Ventura 13.6.5, tvOS 17.4, visionOS 1.1, watchOS 10.4. An attacker with arbitrary kernel read and write capability may be able to bypass kernel memory protections. Apple is aware of a report that this issue may have been exploited.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
Affected versions
- Apple iOS and iPadOS
fixed in 16.7.6; fixed in 17.4
- Apple macOS
fixed in 12.7.4; fixed in 13.6.5; fixed in 14.4
- Apple tvOS
fixed in 17.4
- Apple visionOS
fixed in 1.1
- Apple watchOS
fixed in 10.4