Kernel crash via stale waitqueue entry access
Published Oct 29, 2024 · Updated Aug 5, 2026
Use-after-free in affected Linux kernel versions allows local users to crash the kernel through concurrent block I/O. rq_qos_wake_function deletes a stack-backed waitqueue entry before calling wake_up_process, allowing rq_qos_wait to return and invalidate data->task. An unprivileged local user able to generate concurrent writes, fsync calls, or hole punching on an affected block device can trigger a kernel oops and corrupt kernel state.
Summary
What happened
Use-after-free in affected Linux kernel versions allows local users to crash the kernel through concurrent block I/O. rq_qos_wake_function deletes a stack-backed waitqueue entry before calling wake_up_process, allowing rq_qos_wait to return and invalidate data->task. An unprivileged local user able to generate concurrent writes, fsync calls, or hole punching on an affected block device can trigger a kernel oops and corrupt kernel state.
The record
- CVE
- CVE-2024-50082
- Published
- Oct 29, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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=38cfb5a45ee013bfab5d1ae4c4738815e744b440 <04f283fc16c8d5db641b6bffd2d8310aa7eccebc
- Affected versionversion=38cfb5a45ee013bfab5d1ae4c4738815e744b440 <3bc6d0f8b70a9101456cf02ab99acb75254e1852
- Affected versionversion=38cfb5a45ee013bfab5d1ae4c4738815e744b440 <455a469758e57a6fe070e3e342db12e4a629e0eb
- Affected versionversion=38cfb5a45ee013bfab5d1ae4c4738815e744b440 <4c5b123ab289767afe940389dbb963c5c05e594e
- Affected versionversion=38cfb5a45ee013bfab5d1ae4c4738815e744b440 <b5e900a3612b69423a0e1b0ab67841a1fb4af80f
- Affected versionversion=38cfb5a45ee013bfab5d1ae4c4738815e744b440 <d04b72c9ef2b0689bfc1057d21c4aeed087c329f
- Affected versionversion=38cfb5a45ee013bfab5d1ae4c4738815e744b440 <e972b08b91ef48488bae9789f03cfedb148667fb
- Affected versionversion=4.19
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.
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