Loading vulnerability…
CVE-2025-22068 is a use-after-free vulnerability in the Linux kernel ublk block driver. When a ublk queue is frozen, the driver did not reliably set the queue cancellation-state flag. Consequently, ublk_queue_rq() could make an unsafe request-dispatch decision involving uring_cmd and io_uring command-completion processing. The corrected behavior sets the cancellation state during queue freezing, ensuring pending commands follow cancellation and completion paths safely. The vulnerable behavior was introduced in Linux kernel 6.7.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel ublk flaw involving failure to set ubq->canceling when a queue is frozen.
A Linux kernel ublk queue-state handling flaw addressed by ensuring ubq->canceling is set when a queue is frozen.
A Linux kernel ublk driver use-after-free vulnerability involving request dispatch through uring_cmd when a queue is frozen. The fix sets ubq->canceling on queue freeze so the flag is reliably observed and outstanding uring_cmd operations are cancelled and completed safely.
A Linux kernel ublk driver use-after-free vulnerability caused by failure to reliably set the ubq->canceling flag when a queue is frozen. An attacker requires local access and access to the relevant ublk ioctl requests to trigger it.
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.