CVE-2024-41056 is an out-of-bounds read vulnerability in the Linux kernel firmware cs_dsp component when parsing Version 1 WMFW firmware files. Algorithm and coefficient names are stored in fixed-size arrays and are expected to be NUL-terminated. The affected code used strlen(), which can continue reading beyond the array boundary if a malformed name field lacks a NUL terminator. The fix replaces unbounded strlen() calls with bounded strnlen() calls.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel cs_dsp firmware parser string-length handling issue in V1 WMFW files.
A Linux kernel cs_dsp firmware-parser vulnerability involving name fields in version 1 WMFW files.
A Linux kernel cs_dsp firmware-parser vulnerability involving name fields in version 1 WMFW files.
A Linux kernel cs_dsp firmware-parser flaw in which strlen() was used on fixed-size algorithm and coefficient name arrays in V1 WMFW firmware files. A malformed file without a NUL terminator could cause reads beyond the array boundary; the fix replaces strlen() with bounded strnlen().
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.