Privilege escalation via incorrect io_uring task identity
Published May 31, 2022 · Updated Aug 3, 2024
Use-after-free in io_uring in The Linux Kernel Organization Linux Kernel 5.10 and 5.11 allows local users to crash or gain privileges. Request preparation uses the current task's identity instead of the originating request task, causing type confusion and an invalid free during teardown. Exploitation requires local code execution, an IORING_SETUP_IOPOLL ring, and concurrent submissions by multiple tasks; success yields a system crash or elevated privileges.
Summary
What happened
Use-after-free in io_uring in The Linux Kernel Organization Linux Kernel 5.10 and 5.11 allows local users to crash or gain privileges. Request preparation uses the current task's identity instead of the originating request task, causing type confusion and an invalid free during teardown. Exploitation requires local code execution, an IORING_SETUP_IOPOLL ring, and concurrent submissions by multiple tasks; success yields a system crash or elevated privileges.
The record
- CVE
- CVE-2022-1786
- Published
- May 31, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 31, 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=kernel v5.10 and v5.11
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
- Minimal crashing proof of conceptproof of concept · demonstrated
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