LiveActive security incident?Get immediate response
CVE Record

CVE-2025-39959: ASoC: amd: acp: Fix incorrect retrival of acp_chip_info

In the Linux kernel, the following vulnerability has been resolved: ASoC: amd: acp: Fix incorrect retrival of acp_chip_info Use dev_get_drvdata(dev->parent) instead of dev_get_platdata(dev) to correctly obtain acp_chip_info members in the acp I2S driver. Previously, some members were not updated properly due to incorrect data access, which could potentially lead to null pointer dereferences. This issue was missed in the earlier commit ("ASoC: amd: acp: Fix NULL pointer deref in acp_i2s_set_tdm_slot"), which only addressed set_tdm_slot(). This change ensures that all relevant functions correctly retrieve acp_chip_info, preventing further null pointer dereference issues.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the AMD ACP audio driver. The driver could read chip information from the wrong place, leaving fields unset and potentially causing null pointer crashes. The business risk is mainly system stability on affected Linux systems using this driver, not confirmed remote compromise.

Executive priority

Treat as a normal kernel maintenance item unless affected AMD audio endpoints are business-critical or showing crashes. There is no sourced evidence of exploitation, but kernel availability bugs should be patched through standard update cycles.

Technical view

The ASoC AMD ACP I2S driver used dev_get_platdata(dev) instead of dev_get_drvdata(dev->parent) to retrieve acp_chip_info. Incorrect data access could leave members stale or unset across relevant functions, creating possible null pointer dereferences. The source says this extends a prior incomplete fix for set_tdm_slot().

Likely exposure

Exposure appears limited to Linux systems on affected kernel versions that use the AMD ACP I2S audio driver path. The bundle lists Linux 6.15, 6.16.9, and 6.17-related version information, but distribution backport status is not provided.

Exploitation context

No active exploitation is supported by the supplied sources, and KEV is false. The bundle provides no CVSS, CWE, exploit report, or attacker prerequisites. The documented impact is potential null pointer dereference, which most directly suggests availability risk.

Researcher notes

The source evidence is narrow: CVE text and two kernel stable commits. It supports a driver null dereference risk, not privilege escalation or remote attack. Further analysis should inspect the referenced commits and downstream distro advisories before rating broader operational impact.

Mitigation direction

  • Apply vendor or distribution kernel updates containing the referenced stable fixes.
  • Check kernel vendor advisories for exact fixed package versions.
  • Prioritize affected endpoints where AMD ACP audio support is enabled.
  • Track downstream backports if using enterprise or LTS kernels.

Validation and detection

  • Inventory Linux kernel versions across managed systems.
  • Identify systems loading AMD ACP or ACP I2S audio drivers.
  • Compare deployed kernels against vendor fixed-package advisories.
  • Confirm the referenced stable commits are present or backported.
  • Review crash logs for AMD ACP null pointer dereference indicators.
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-2025-39959 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
LinuxLinuxe3933683b25e2cc94485da4909e3338e1a177b39, e3933683b25e2cc94485da4909e3338e1a177b39unaffected
LinuxLinux6.15, 0, 6.16.9, 6.17affected
Weakness

CWE details

No CWE listed

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