Kernel code execution via unsafe memory handling
Published Jul 29, 2024 · Updated Mar 19, 2025
Memory corruption in Apple IOUserEthernet before iOS 17, iPadOS 17, macOS 14, watchOS 10, and tvOS 17 allows local users to run kernel code. Apple discloses only that IOUserEthernet performs unsafe memory handling; the exact operation and attacker-controlled input path are not public. A locally installed app must reach the component, and successful exploitation grants kernel privileges on an affected device.
Summary
What happened
Memory corruption in Apple IOUserEthernet before iOS 17, iPadOS 17, macOS 14, watchOS 10, and tvOS 17 allows local users to run kernel code. Apple discloses only that IOUserEthernet performs unsafe memory handling; the exact operation and attacker-controlled input path are not public. A locally installed app must reach the component, and successful exploitation grants kernel privileges on an affected device.
The record
- CVE
- CVE-2023-40396
- Published
- Jul 29, 2024
- Updated
- Mar 19, 2025
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-77, T1404, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 2024CVE publishedPublication date reported by the CVE source.
- Mar 19, 2025Record 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.0
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