Skip to content
Noroxi
CVE-2026-64481· NVD / CVE Program· CNA Linux

ALSA: hda/cs35l41: Fix firmware load work teardown

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3e339c88b8c3044919fd1936a8b23124285d0de6, 8947215c0136c9d905e4a46d824824f8b48a2e5b, b65020d5398f499c09498c9786dba6d67ae57664.

Low priority for now. Upgrade to Linux Linux 3e339c88b8c3044919fd1936a8b23124285d0de6, 8947215c0136c9d905e4a46d824824f8b48a2e5b, b65020d5398f499c09498c9786dba6d67ae57664 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Oct 21, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64481

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.0affected
    • 47ceabd99a28399f8971f4ca0a37ebc0a21dd2a8 and later · before 3e339c88b8c3044919fd1936a8b23124285d0de6affected · git
    • 47ceabd99a28399f8971f4ca0a37ebc0a21dd2a8 and later · before 8947215c0136c9d905e4a46d824824f8b48a2e5baffected · git
    • 47ceabd99a28399f8971f4ca0a37ebc0a21dd2a8 and later · before ce0a903d0591e3e2c790c5b628802b08d1b287ccaffected · git
    • 47ceabd99a28399f8971f4ca0a37ebc0a21dd2a8 and later · before d6a40a4d083ef74d00c8f9516cb5ff07ac70720baffected · git
    • 47ceabd99a28399f8971f4ca0a37ebc0a21dd2a8 and later · before b65020d5398f499c09498c9786dba6d67ae57664affected · git
    • before 6.0not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver
    • 6.12.97 and later · up to and including 6.12.*not affected · semver
    • 6.18.39 and later · up to and including 6.18.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2

+55

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-64463Jul 25, 2026 · usb: typec: tcpci_rt1711h: unregister TCPCI port with devres
    31Monitor
  • ← EarlierCVE-2026-64475Jul 25, 2026 · vfio/pci: Release the VGA arbiter client on register_device() failure
    35Monitor
  • Later →CVE-2026-64485Jul 25, 2026 · ALSA: compress: Fix task creation error unwind
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3e339c88b8c3044919fd1936a8b23124285d0de6Vendor (CNA)
Linux Linux8947215c0136c9d905e4a46d824824f8b48a2e5bVendor (CNA)
Linux Linuxb65020d5398f499c09498c9786dba6d67ae57664Vendor (CNA)
Linux Linuxce0a903d0591e3e2c790c5b628802b08d1b287ccVendor (CNA)
Linux Linuxd6a40a4d083ef74d00c8f9516cb5ff07ac70720bVendor (CNA)
almalinux:kernel6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.100-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-645230 days apartnet/handshake: Take a long-lived file reference at submit
    39Monitor
  • CVE-2026-645301 days apartnet/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle
    39Monitor
  • CVE-2026-645412 days apartnet/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket
    39Monitor
  • CVE-2026-639226 days apartipv6: exthdrs: refresh nh after handling HAO option
    39Monitor
  • CVE-2026-639796 days apartnet/handshake: hand off the pinned file reference to accept_doit
    39Monitor
  • CVE-2026-6456410 days apartsctp: don't free the ASCONF's own transport in DEL-IP processing
    39Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records