Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 3cac6eebea9b4bc5f041e157e45c76e212ad6759 – < 4931c09d83877dc350106bae745321c3f295129b
    • affected c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 – < 96d51b8c5a909937d41f9c03495188d4190f877d
    • affected c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 – < f2435a46dfa1a5693cf2664afd022db66ee58121
    • affected c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 – < 6b512a5330ef1a41db7aff4b80c4e952b8d52f17
    • affected c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 – < 17661c67b206612cb3ba65d5ae726cd2015d0a53
    • affected 6ee66295542f88e5179439f60053de792df3f90e
    • affected d153e8b154f9746ac969c85a4e6474760453647c
    • affected 6.6.23 – < 6.6.154
    • affected 6.1.191 – < 6.2
    • affected 6.7.11 – < 6.8
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 6.6.154 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.46 – ≤ 6.18.*
    • unaffected 7.1.10 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80581 badge
[![CVE-2026-80581](https://cveledger.app/badge/CVE-2026-80581.svg)](https://cveledger.app/cve/CVE-2026-80581)

Record last updated .