LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57805: ASoC: SOF: Intel: hda-dai: Do not release the link DMA on STOP

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Intel: hda-dai: Do not release the link DMA on STOP The linkDMA should not be released on stop trigger since a stream re-start might happen without closing of the stream. This leaves a short time for other streams to 'steal' the linkDMA since it has been released. This issue is not easy to reproduce under normal conditions as usually after stop the stream is closed, or the same stream is restarted, but if another stream got in between the stop and start, like this: aplay -Dhw:0,3 -c2 -r48000 -fS32_LE /dev/zero -d 120 CTRL+z aplay -Dhw:0,0 -c2 -r48000 -fS32_LE /dev/zero -d 120 then the link DMA channels will be mixed up, resulting firmware error or crash.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel audio-driver flaw. Under a narrow timing condition, one audio stream can release a DMA channel too early, allowing another stream to take it and causing channel mix-ups, firmware errors, or a crash. The public record does not show active exploitation or remote compromise.

Executive priority

Treat as a targeted availability risk, not an emergency remote-compromise issue. Patch through normal kernel maintenance, with higher priority for fleets where audio firmware crashes affect user productivity, kiosk stability, or operational endpoints.

Technical view

CVE-2024-57805 affects Linux ASoC SOF Intel HDA DAI handling. The link DMA is released on STOP even though a stream may restart without closing, creating a race where another stream can acquire it. Upstream resolved this by not releasing link DMA on STOP.

Likely exposure

Exposure appears limited to Linux systems using the affected kernel code path for Intel SOF/HDA audio. The CVE metadata identifies Linux kernel affected versions including the 6.12 line and 6.13. Confirm exact distro backports rather than relying only on upstream version strings.

Exploitation context

The source describes a difficult-to-reproduce local timing condition involving overlapping audio stream lifecycle events. CISA KEV is false in the provided bundle, and no cited source states active exploitation in the wild.

Researcher notes

Evidence is limited to upstream kernel CVE text and stable commit references. No CVSS, CWE, exploit status, or distro-specific fixed versions are provided. The interesting condition is the STOP-to-restart window where link DMA ownership can be reassigned incorrectly.

Mitigation direction

  • Update to a vendor kernel containing the referenced upstream stable fixes.
  • Check Linux distribution advisories for backported fixes and affected build numbers.
  • Prioritize laptops, workstations, and embedded systems using Intel SOF/HDA audio.
  • If no update is available, monitor vendor guidance for supported mitigations.

Validation and detection

  • Inventory Linux kernel versions across systems with Intel SOF/HDA audio hardware.
  • Verify whether deployed kernels include the referenced stable commits.
  • Review vendor advisories for exact fixed package versions.
  • Check system logs for audio firmware errors or crashes after stream restarts.
Prepared
Confidence
medium
Sources
4

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-57805 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
0ADP providers
3Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxab5593793e9088abcddce30ba8e376e31b7285fd, ab5593793e9088abcddce30ba8e376e31b7285fd, ec0c7735dd014e54e55bc3bf4ed2e73d56bb00b3, 6.11.6unaffected
LinuxLinux6.12, 0, 6.12.8, 6.13affected
Weakness

CWE details

No CWE listed

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