Loading vulnerability…
CVE-2023-4130 is a Linux kernel vulnerability in ksmbd, specifically in the smb2_set_ea() path that parses FILE_FULL_EA_INFORMATION requests containing multiple smb2_ea_info entries. The flaw is caused by incorrect validation of the length of the next extended attribute buffer before accessing the next entry. ksmbd locates the next smb2_ea_info structure using the current entry's NextEntryOffset, but the code validated using the next variable rather than buf_len. Because next represents the start offset of the current EA derived from the previous entry, this can result in improper bounds checking when walking the EA list. The issue was resolved by validating the buffer length using buf_len before accessing the next EA entry.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (POC) exploit for two Linux kernel KSMBD vulnerabilities (CVE-2023-52440 and CVE-2023-4130), enabling remote code execution (RCE) via a 0-click attack. The exploit targets the KSMBD kernel module on Linux 6.1.45 (and likely other vulnerable versions), requiring a custom kernel configuration and a patched impacket library (patch provided as impacket.diff). The build-image.sh script automates the creation of a vulnerable Debian-based VM image with KSMBD and a test user/share. The main exploit logic is in poc.py, which uses the patched impacket library to interact with the SMB server, leak heap memory, and craft a payload that hijacks control flow to execute a reverse shell (nc.traditional -e /bin/sh) as root. The exploit is complex, involving heap spraying, memory leaks, and vtable hijacking, and is intended for research purposes only. The repository is well-structured, with clear separation between the environment setup, library patching, and exploit logic.
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.
12 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.