CVE-2022-48760 is a synchronization flaw in the Linux kernel USB core. On SMP systems, concurrent execution of usb_kill_urb() and __usb_hcd_giveback_urb() lacks the memory ordering required between updates to a URB rejection state and reference/use count. The resulting store-buffering race can allow the teardown CPU to observe a stale use count while the completion CPU observes a stale rejection state. The completion path then omits the required wake-up, leaving the teardown operation indefinitely blocked. Equivalent access patterns affect usb_poison_urb() and the failure path of usb_hcd_submit_urb().
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel USB core synchronization flaw that can cause a hang.
A Linux kernel USB core vulnerability that can cause a hang in usb_kill_urb; it was resolved by adding memory barriers.
A Linux kernel USB-core synchronization flaw (CWE-820) caused by missing memory barriers in a store-buffering pattern. It can leave processes indefinitely waiting in usb_kill_urb(), resulting in a denial-of-service/hang condition.
A Linux kernel USB core race condition caused by insufficient memory barriers in concurrent URB rejection and completion processing. Store-buffering reordering can leave usb_kill_urb() permanently waiting for a URB completion notification, resulting in a kernel-level hang/denial of service.
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.