Loading vulnerability…
CVE-2024-50151 is an out-of-bounds write vulnerability in the Linux kernel SMB client when constructing encrypted SMB2_IOCTL requests. SMB2_ioctl_init() allocates a 448-byte buffer for the request in the first I/O vector. When SMB encryption is enabled, smb2_set_next_command() consolidates compound-request buffers into a single I/O vector. An input buffer larger than 328 bytes can cause this consolidation to write beyond the allocated buffer, corrupting kernel heap memory. The vulnerability can be triggered by creating a symbolic link with a long target on an encrypted SMB share.
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.
An out-of-bounds write in the Linux kernel SMB client occurs while constructing encrypted compound SMB2_IOCTL requests. The reference demonstrates the fault through symlink creation on an encrypted CIFS mount. It assigns a CVSS v3 score of 7.8, indicating local exploitation requiring low privileges and potentially high confidentiality, integrity, and availability impacts. The prescribed fix is updating the affected Google COS kernel packages to version 18613.75.60 or later.
Out-of-bounds accesses while Linux kernel SMB client builds SMB2 IOCTL requests.
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.