# ASoC: amd: acp: Fix incorrect retrival of acp_chip_info

CVE record · `CVE-2025-39959`

- **Identifiers:** `CVE-2025-39959`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 9 Oct 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 9 Oct 2025, 09:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `e3933683b25e2cc94485da4909e3338e1a177b39 to before 65c5cfbd6d938f77a0df3c34855a4f7d8a61fd10` (git)
  - affected: `e3933683b25e2cc94485da4909e3338e1a177b39 to before d7871f400cad1da376f1d7724209a1c49226c456` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.15`
  - unaffected: `before 6.15` (semver)
  - unaffected: `6.16.9 to 6.16.*, inclusive` (semver)
  - unaffected: `6.17 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's AMD ACP audio driver (ASoC) is affected in version 6.15. The source gives few details on who can trigger it, only that incorrect data access could lead to null pointer dereferences. Upgrade to kernel 6.16.9 or later in the 6.16 series, or to 6.17 or later.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0013, the 2nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 9 Oct 2025, 09:47 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-39959)
- 9 Oct 2025, 10:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-39959)

## Sources

- [CVE List: CVE-2025-39959](https://www.cve.org/CVERecord?id=CVE-2025-39959)
- [NVD: CVE-2025-39959](https://nvd.nist.gov/vuln/detail/CVE-2025-39959)

### References from the CNA

- <https://git.kernel.org/stable/c/65c5cfbd6d938f77a0df3c34855a4f7d8a61fd10>
- <https://git.kernel.org/stable/c/d7871f400cad1da376f1d7724209a1c49226c456>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-39959>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-39959/>. Everything for agents: <https://agentprime.io/llms.txt>.
