Kernel crash via io_uring context use-after-free
Published Jun 7, 2021 · Updated Aug 4, 2024
Use-after-free in Linux kernel io_uring before 5.8.2 allows local users to crash the kernel through asynchronous task work. io_async_task_func queues and executes task work without retaining the io_ring_ctx reference, allowing the context to be freed before a later dereference. A local low-privileged user must exercise io_uring; the demonstrated result is an invalid kernel-memory read and kernel crash.
Summary
What happened
Use-after-free in Linux kernel io_uring before 5.8.2 allows local users to crash the kernel through asynchronous task work. io_async_task_func queues and executes task work without retaining the io_ring_ctx reference, allowing the context to be freed before a later dereference. A local low-privileged user must exercise io_uring; the demonstrated result is an invalid kernel-memory read and kernel crash.
The record
- CVE
- CVE-2020-36387
- Published
- Jun 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- syzbot io_uring crash reproducerproof 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