LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27057: ASoC: SOF: ipc4-pcm: Workaround for crashed firmware on system suspend

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc4-pcm: Workaround for crashed firmware on system suspend When the system is suspended while audio is active, the sof_ipc4_pcm_hw_free() is invoked to reset the pipelines since during suspend the DSP is turned off, streams will be re-started after resume. If the firmware crashes during while audio is running (or when we reset the stream before suspend) then the sof_ipc4_set_multi_pipeline_state() will fail with IPC error and the state change is interrupted. This will cause misalignment between the kernel and firmware state on next DSP boot resulting errors returned by firmware for IPC messages, eventually failing the audio resume. On stream close the errors are ignored so the kernel state will be corrected on the next DSP boot, so the second boot after the DSP panic. If sof_ipc4_trigger_pipelines() is called from sof_ipc4_pcm_hw_free() then state parameter is SOF_IPC4_PIPE_RESET and only in this case. Treat a forced pipeline reset similarly to how we treat a pcm_free by ignoring error on state sending to allow the kernel's state to be consistent with the state the firmware will have after the next boot.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2024-27057 is a Linux kernel audio/DSP reliability flaw. If audio is active during system suspend and the Sound Open Firmware crashes, the kernel and firmware can disagree about pipeline state after resume, causing audio resume failures. Public sources do not indicate remote code execution, privilege escalation, or active exploitation.

Executive priority

Treat as routine patch management unless audio reliability is business-critical. The available evidence points to availability and user-experience impact rather than data compromise. Patch through normal kernel update channels and prioritize fleets where suspend/resume audio failures affect operations.

Technical view

The flaw is in Linux ASoC SOF ipc4-pcm handling. During suspend, sof_ipc4_pcm_hw_free() resets pipelines because the DSP powers off. If firmware crashes, sof_ipc4_set_multi_pipeline_state() can fail, leaving kernel and firmware states misaligned. The fix treats forced pipeline reset like pcm_free by ignoring the state-send error for SOF_IPC4_PIPE_RESET.

Likely exposure

Exposure appears limited to Linux systems using the affected ASoC SOF IPC4 audio path. The source lists Linux kernel versions including 5.19, 6.6.23, 6.7.11, and 6.8 as affected, with stable kernel commits referenced as fixes. Distribution backports may change practical exposure.

Exploitation context

No KEV listing and no cited source reports active exploitation. The described trigger requires suspend while audio is active and a firmware crash or reset failure condition. The documented impact is audio resume failure and state inconsistency, not attacker-controlled code execution.

Researcher notes

The record lacks CVSS and CWE data. The fix is a state-consistency change around forced pipeline reset after firmware crash during suspend. Available sources do not support claims of remote exploitation, privilege escalation, or broad kernel compromise.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable commits.
  • Check Linux distribution advisories for backported fixes.
  • Prioritize affected laptops, workstations, and devices relying on SOF IPC4 audio.
  • If unpatched, follow vendor guidance for operational workarounds.

Validation and detection

  • Inventory Linux kernel versions on systems using SOF-based audio.
  • Confirm whether the referenced stable commits are present or backported.
  • Review suspend/resume audio failures and SOF IPC errors in system logs.
  • Validate audio resumes normally after applying the updated kernel.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-27057 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxceb89acc4dc8f071f63f8d64442c7a5d768e4c9d, ceb89acc4dc8f071f63f8d64442c7a5d768e4c9d, ceb89acc4dc8f071f63f8d64442c7a5d768e4c9dunaffected
LinuxLinux5.19, 0, 6.6.23, 6.7.11, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.