Loading vulnerability…
CVE-2024-58077 affects the Linux kernel ALSA System-on-Chip (ASoC) PCM implementation in sound/soc/soc-pcm.c. The .prepare callback used the shared soc_pcm_ret() error handler, which suppresses -EINVAL errors. That suppression was intended only for invalid parameters originating in userspace, to avoid excessive logging that could exhaust syslog or disk resources. Applying the behavior to .prepare was overly broad and caused callback-generated -EINVAL errors to be silently ignored. The upstream fix removes use of soc_pcm_ret() from the .prepare callback.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel ASoC PCM prepare-callback handling flaw.
Linux kernel ASoC PCM callback handling flaw.
A Linux kernel ASoC soc-pcm error-handling issue in which the common soc_pcm_ret() function suppressed -EINVAL errors too broadly, including from the .prepare callback. The fix avoids using soc_pcm_ret() for that callback.
A Linux kernel ALSA System-on-Chip (ASoC) soc-pcm flaw involving use of soc_pcm_ret() in the .prepare callback. The error-handling behavior could create a local denial-of-service availability impact through uncontrolled resource consumption/logging-related behavior.
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.