LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23190: ASoC: amd: fix memory leak in acp3x pdm dma ops

In the Linux kernel, the following vulnerability has been resolved: ASoC: amd: fix memory leak in acp3x pdm dma ops

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-23190 is a Linux kernel issue in AMD audio support. The public record says a memory leak was fixed in ASoC AMD acp3x PDM DMA operations. Business impact is unclear because no CVSS score, CWE, exploitation evidence, or detailed trigger conditions are provided.

Executive priority

Handle through normal kernel patch management unless affected AMD audio systems are business-critical or unstable. There is no sourced evidence of active exploitation, but kernel memory leaks can still affect reliability and should not be ignored.

Technical view

The vulnerability is described only as a resolved memory leak in the Linux kernel ASoC AMD acp3x PDM DMA ops path. References are Linux stable commits. The source bundle does not describe privilege requirements, attack vector, denial-of-service impact, or whether the affected driver must be loaded.

Likely exposure

Exposure likely depends on Linux kernel version, AMD ACP3x audio hardware, and whether the relevant ASoC/PDM DMA driver is built and used. The CVE record lists Linux as affected across multiple kernel version entries, but distro package mapping is not provided.

Exploitation context

No active exploitation is supported by the provided sources. The CVE is not marked in KEV, and the bundle provides no public exploit, proof of concept, or attacker workflow. Treat exploitation likelihood as unproven pending vendor or distro advisories.

Researcher notes

The record is sparse: no CVSS, CWE, detailed impact, trigger path, or distribution mapping. Analysis should focus on commit presence, driver configuration, and affected hardware. Do not infer remote reachability or privilege escalation from the current evidence.

Mitigation direction

  • Track Linux stable fixes referenced by the CVE record.
  • Apply vendor or distribution kernel updates when available.
  • Prioritize systems using AMD ACP3x audio hardware or related drivers.
  • Check vendor advisories before creating compensating controls.
  • Avoid direct deployment workarounds not documented by kernel or distro maintainers.

Validation and detection

  • Inventory kernel versions across Linux assets.
  • Identify systems with AMD ACP3x or related ASoC audio drivers.
  • Check whether referenced stable commits are included in deployed kernels.
  • Review distribution security advisories for package-specific fixed versions.
  • Monitor for memory pressure or driver instability on affected hardware.
Prepared
Confidence
medium
Sources
9

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-2026-23190 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
8Source 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
LinuxLinux4a767b1d039a855c491c4853013804323c06f728, 4a767b1d039a855c491c4853013804323c06f728, 4a767b1d039a855c491c4853013804323c06f728, 4a767b1d039a855c491c4853013804323c06f728, 4a767b1d039a855c491c4853013804323c06f728, 4a767b1d039a855c491c4853013804323c06f728, 4a767b1d039a855c491c4853013804323c06f728unaffected
LinuxLinux5.8, 0, 5.10.250, 5.15.200, 6.1.163, 6.6.124, 6.12.70, 6.18.10, 6.19affected
Weakness

CWE details

No CWE listed

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