ALSA: hda/cs35l41: Fix firmware load work teardown
CVE-2026-64481 · published 25 Jul 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-64481?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 47ceabd99a28399f8971f4ca0a37ebc0a21dd2a8 to < 3e339c88b8c3044919fd1936a8b23124285d0de6, 47ceabd99a28399f8971f4ca0a37ebc0a21dd2a8 to < 8947215c0136c9d905e4a46d824824f8b48a2e5b, 47ceabd99a28399f8971f4ca0a37ebc0a21dd2a8 to < ce0a903d0591e3e2c790c5b628802b08d1b287cc, 47ceabd99a28399f8971f4ca0a37ebc0a21dd2a8 to < d6a40a4d083ef74d00c8f9516cb5ff07ac70720b
- Linux Linux: 6.0
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
ALSA: hda/cs35l41: Fix firmware load work teardown
cs35l41_hda creates ALSA controls whose private data points at the
cs35l41_hda object. The firmware load control can also queue
fw_load_work.
Those controls are not removed on component unbind, and device remove
only cancels fw_load_work through cs35l41_remove_dsp(). That helper is
skipped when halo_initialized is false. With firmware_autostart
disabled, a firmware load can be requested before the DSP has been
initialized. If the component or device is removed before the queued
work runs, the worker can run after teardown and dereference driver
state that is no longer valid.
Track the created controls and remove them on unbind so no new control
callback can reach the driver data or queue more work. Then cancel
fw_load_work to drain any request that was already queued. Also cancel
the work unconditionally during device remove before runtime PM teardown.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/3e339c88b8c3044919fd1936a8b23124285d0de6
- git.kernel.org/stable/c/8947215c0136c9d905e4a46d824824f8b48a2e5b
- git.kernel.org/stable/c/ce0a903d0591e3e2c790c5b628802b08d1b287cc
- git.kernel.org/stable/c/d6a40a4d083ef74d00c8f9516cb5ff07ac70720b
- git.kernel.org/stable/c/b65020d5398f499c09498c9786dba6d67ae57664
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON