Kernel code execution via out-of-bounds driver write
Published May 26, 2022 · Updated Aug 3, 2024
Out-of-bounds write in the Intel Graphics Driver in Apple macOS allows local users to execute arbitrary code with kernel privileges. The driver insufficiently validates application-supplied input before writing memory beyond a buffer boundary; Apple has not disclosed the affected function. Execution requires a user to run a malicious application, after which its code runs with kernel privileges.
Summary
What happened
Out-of-bounds write in the Intel Graphics Driver in Apple macOS allows local users to execute arbitrary code with kernel privileges. The driver insufficiently validates application-supplied input before writing memory beyond a buffer boundary; Apple has not disclosed the affected function. Execution requires a user to run a malicious application, after which its code runs with kernel privileges.
The record
- CVE
- CVE-2022-26756
- Published
- May 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- Security Update Catalina
- Classifications
- CWE-787, T1204.002, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=unspecified <2022
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