CVE Intelligence
Unknown

CVE-2026-80581 — ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout Ignore IPC errors for pipeline state change if the firmware state is crashed or the IPC has timed out. If the firmware has crashed the kernel still needs to go through the state changes to reset its internal to be able to correctly work the next time the DSP is booted up. The case with IPC timeout is a bit more problematic, but it has been rootcaused to be the result of system scheduling blockage and the firmware did actually received and handled the message, but the reply handling got blocked by issues outside of the SOF stack. So far the best way to handle this is to continue with setting the state.

Published Aug 26, 2026 · Updated Oct 21, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.21%
ahead of 11% of scored CVEs · Oct 26, 2026
Affects
Linux
Linux
CVSS base
—
Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux ≥ 3cac6eebea9b4bc5f041e157e45c76e212ad6759 and < 4931c09d83877dc350106bae745321c3f295129b≥ c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 and < f2435a46dfa1a5693cf2664afd022db66ee58121≥ c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 and < 6b512a5330ef1a41db7aff4b80c4e952b8d52f17≥ c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 and < 17661c67b206612cb3ba65d5ae726cd2015d0a53version d153e8b154f9746ac969c85a4e6474760453647c≥ 6.6.23 and < 6.6.154≥ 6.7.11 and < 6.8version 6.8
and 1 more ≥ c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 and < 96d51b8c5a909937d41f9c03495188d4190f877d
Vulnerable CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 26, 2026 · 11 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · linux/linux
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • Affected products added · linux/linux
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Received
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Aug 26, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 21, 2026 – Oct 21, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

7 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 1d
  • Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 1d
  • Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 1d
  • Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 1d
  • Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 1d
  • Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CVSS score published by NVD, the CNA, CISA or GitHub so far.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-80581 is "ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.