CVE-2024-41039 is an out-of-bounds read condition in the Linux kernel firmware: cs_dsp component while parsing WMFW firmware headers. The original firmware-buffer length validation checked the combined size of wmfw_header, wmfw_adsp1_sizes, and wmfw_footer. However, ADSP2 and Halo Core firmware use wmfw_adsp2_sizes, which is four bytes larger than the ADSP1-specific structure. Consequently, the check could accept an insufficient buffer before the larger ADSP2/Halo Core header structure was accessed. The fix validates wmfw_header, the applicable firmware-size structure, and wmfw_footer separately before use.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel vulnerability covered by the security update.
Linux kernel cs_dsp firmware WMFW-header overflow-checking flaw.
Linux kernel cs_dsp firmware handling flaw involving insufficient overflow checking of WMFW headers.
Linux kernel cs_dsp firmware flaw involving insufficient overflow checking of a WMFW header.
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.