Local kernel crash via stale wait-queue entry
Published Dec 23, 2022 · Updated Apr 15, 2025
Use-after-free in io_sqpoll_wait_sq in Linux kernel 5.10 through 5.10.154 allows local users to crash the kernel via io_uring. The function jumps to its out path when ctx->sqo_dead is set, skipping finish_wait and leaving a stack wait_queue_entry linked after its lifetime. Triggering requires low-privileged local access and a forked process that quickly closes a copied io_uring descriptor; the bounded result is a kernel crash and service interruption.
Summary
What happened
Use-after-free in io_sqpoll_wait_sq in Linux kernel 5.10 through 5.10.154 allows local users to crash the kernel via io_uring. The function jumps to its out path when ctx->sqo_dead is set, skipping finish_wait and leaving a stack wait_queue_entry linked after its lifetime. Triggering requires low-privileged local access and a forked process that quickly closes a copied io_uring descriptor; the bounded result is a kernel crash and service interruption.
The record
- CVE
- CVE-2022-47946
- Published
- Dec 23, 2022
- Updated
- Apr 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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?
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
- io_sqpoll_wait_sq fork-and-exit trigger descriptionproof of concept · unverified
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