Loading vulnerability…
Micron Crucial MX500 Series SSDs running firmware M3CR046 contain a buffer overflow condition in the drive controller’s handling of ATA command/packet input. An attacker on the host can trigger the flaw by sending specially crafted ATA packets/commands to the SSD controller, leading to memory corruption within the controller firmware. The supplier indicates the issue was fully remediated in December 2024 and that updated firmware is available via Crucial’s official support page.
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 proof-of-concept (POC) exploits for CVE-2024-42642, a set of vulnerabilities in the firmware update mechanism of Crucial MX500 SSDs (SM2259 controller, firmware M3CR046). The repository contains three main exploit programs (src/BUG_1/exploit.c, src/BUG_2/exploit.c, src/BUG_3/exploit.c), each targeting a different bug in the firmware's microcode download handler. The exploits use the libatafw library to send crafted firmware update chunks to the SSD via the ATA PIO DOWNLOAD-MICROCODE (0x92) command. The payloads are sequences of chunked data designed to trigger underflow and bounds-checking bugs, resulting in device hangs or other erratic behavior. The repository also includes a decompiled version of the vulnerable firmware handler for reference. The exploits require local access to the target system and the ability to interact with the SSD device node (e.g., /dev/sdX). No remote or network attack vector is present. The code is operational as a POC and demonstrates denial-of-service and potential firmware corruption scenarios, but does not provide weaponized or automated payloads.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.