The issue was addressed with improved memory handling
Apple iOS and iPadOS · Apple macOS · Apple watchOS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Apple iOS and iPadOS |
| No fix yet |
| Apple macOS |
| No fix yet |
| Apple watchOS |
| No fix yet |
| Apple macOS |
|
Apple iOS and iPadOS · Apple macOS · Apple watchOS
| Product | Affected | Fixed in |
|---|---|---|
| Apple iOS and iPadOS |
| No fix yet |
| Apple macOS |
| No fix yet |
| Apple watchOS |
| No fix yet |
| Apple macOS |
|
| No fix yet |
| Apple iOS and iPadOS |
| No fix yet |
| Apple macOS |
| No fix yet |
The issue was addressed with improved memory handling. This issue is fixed in iOS 17.1 and iPadOS 17.1, macOS Monterey 12.7.1, watchOS 10.1, iOS 16.7.2 and iPadOS 16.7.2, macOS Ventura 13.6.1, macOS Sonoma 14.1. An attacker that has already achieved kernel code execution may be able to bypass kernel memory mitigations.
From the CVE record · apple
A memory-handling issue affects iOS, iPadOS, macOS, and watchOS. An attacker who has already achieved kernel code execution may be able to bypass kernel memory mitigations; the input does not specify an authentication or user-interaction requirement.
Anyone running iOS or iPadOS before 17.1 or 16.7.2, macOS Monterey before 12.7.1, macOS Ventura before 13.6.1, macOS Sonoma before 14.1, or watchOS before 10.1 should check their devices.