Loading vulnerability…
CVE-2025-68263 is a race-condition-driven use-after-free in the Linux kernel ksmbd subsystem, specifically in ipc_msg_send_request(). The function waits for a generic netlink reply using an ipc_msg_table_entry allocated on the stack. The generic netlink response path, via handle_generic_event()/handle_response(), populates entry->response while holding ipc_msg_table_lock. However, ipc_msg_send_request() previously validated and freed entry->response without taking that same lock. Under high concurrency, this creates a race in which handle_response() can still be copying data into entry->response after ipc_msg_send_request() has freed it, resulting in a slab use-after-free in the ksmbd code path. The fix synchronizes access by taking ipc_msg_table_lock while validating and potentially freeing entry->response, removing the hash-table entry under lock, and only returning the final response pointer after the entry has been removed from ipc_msg_table.
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.
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.