Loading vulnerability…
CVE-2024-50082 is a race condition in the Linux kernel blk-rq-qos subsystem between rq_qos_wait() and rq_qos_wake_function(). The vulnerable wake function sets the token state and removes a stack-resident waitqueue entry before calling wake_up_process() using the entry's data->task pointer. A concurrent rq_qos_wait() can observe the removed entry, return from finish_wait(), and reuse its stack storage before the wake function dereferences data->task. The wake function can consequently pass a stale or corrupted task pointer to wake_up_process(). The fix wakes the task before removing the waitqueue entry and uses list_del_init_careful() to synchronize correctly with finish_wait().
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel block request QoS race condition that can cause a crash.
A Linux kernel block request QoS race condition that can cause a crash between rq_qos_wait and rq_qos_wake_function, addressed in the updated RHEL 8 go-toolset container image.
Linux kernel block request QoS race condition between rq_qos_wait and rq_qos_wake_function that can cause a system crash.
A Linux kernel block request QoS race condition between rq_qos_wait and rq_qos_wake_function that can cause a crash.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.