Strix
73.7K

CVE-2026-80581

UnknownEPSS 0.21%

Last modified

CVE-2026-80581 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.21%

11.1th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 3cac6eebea9b4bc5f041e157e45c76e212ad6759, < 4931c09d83877dc350106bae745321c3f295129b; >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2, < 96d51b8c5a909937d41f9c03495188d4190f877d; >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2, < f2435a46dfa1a5693cf2664afd022db66ee58121; >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2, < 6b512a5330ef1a41db7aff4b80c4e952b8d52f17; >= c40aad7c81e5fba34b70123ed7ce3397fa62a4d2, < 17661c67b206612cb3ba65d5ae726cd2015d0a53; 6ee66295542f88e5179439f60053de792df3f90e; d153e8b154f9746ac969c85a4e6474760453647c; >= 6.6.23, < 6.6.154; >= 6.1.191, < 6.2; >= 6.7.11, < 6.8
LinuxLinux6.8

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80581?
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.
How severe is CVE-2026-80581?
Severity scoring for CVE-2026-80581 is pending analysis. The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2026-80581?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-80581?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST