Loading vulnerability…
CVE-2026-52911 is a flaw in the Linux kernel's ksmbd SMB server implementation. During a binding SESSION_SETUP, the connection-wide flag conn->binding is set so ksmbd_session_lookup_all() can locate a session that is not yet present in conn->sessions. The vulnerable behavior is that this connection-wide binding state remains sufficient to enter the global session lookup slowpath, allowing lookup by session ID to resolve sessions other than the one actually bound to the connection. The fix tightens the slowpath so that a returned session must also have the current connection registered in the session's channel xarray (sess->ksmbd_chann_list), which is populated only when binding_session completes successfully in ntlm_authenticate() or krb5_authenticate(). In effect, only sessions that have explicitly accepted the connection as a channel can be resolved through the global 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.
3 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.