Loading vulnerability…
CVE-2026-46185 is an out-of-bounds read vulnerability in the Linux kernel SMB client, in the symlink_data() function. The flaw arises because smb2_check_message() can return success for an SMB2 symlink error response without validating that the response buffer is large enough for struct smb2_err_rsp. As a result, symlink_data() may process a buffer whose iov_len is smaller than the expected error response structure. If the buffer contains only the base 64-byte SMB2 header, subsequent access to fields such as ErrorContextCount and ByteCount reads beyond the end of the received buffer. This is a kernel-space memory safety issue triggered during handling of SMB2 symlink error responses from a server.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability affecting Red Hat Enterprise Linux 10.2 kernel-related packages; the content does not provide technical details beyond listing it in the advisory.
A Linux kernel SMB client vulnerability involving an out-of-bounds read in symlink_data().
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.