Local kernel panic via improper request cancellation
Published Mar 9, 2022 · Updated Aug 3, 2024
Improper cancellation in Linux Kernel before 5.15-rc1 allows local users to crash the system through io_uring requests. When io_wqe_create_worker() fails after io_wqe_insert_work() has enqueued a request, io_wqe_enqueue() directly calls io_run_cancel() even though another worker can execute that request during cancellation. The trigger requires permission to submit io_uring work and worker-creation failure under resource pressure; successful triggering causes a kernel panic.
Summary
What happened
Improper cancellation in Linux Kernel before 5.15-rc1 allows local users to crash the system through io_uring requests. When io_wqe_create_worker() fails after io_wqe_insert_work() has enqueued a request, io_wqe_enqueue() directly calls io_run_cancel() even though another worker can execute that request during cancellation. The trigger requires permission to submit io_uring work and worker-creation failure under resource pressure; successful triggering causes a kernel panic.
The record
- CVE
- CVE-2021-4023
- Published
- Mar 9, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-200, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 9, 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 versions prior to 5.15-rc1
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