LiveActive security incident?Get immediate response
CVE Record

CVE-2025-40013: ASoC: qcom: audioreach: fix potential null pointer dereference

In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: audioreach: fix potential null pointer dereference It is possible that the topology parsing function audioreach_widget_load_module_common() could return NULL or an error pointer. Add missing NULL check so that we do not dereference it.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in Qualcomm audio support. A missing NULL check during audio topology parsing could make the kernel dereference an invalid pointer. The available sources do not provide CVSS, confirmed impact, or exploitation evidence, so treat it as a stability and availability risk until vendor guidance clarifies severity.

Executive priority

Handle through normal kernel patch governance unless you operate Qualcomm audio-dependent Linux fleets. There is no cited active exploitation, but kernel NULL dereferences can affect availability and should not be ignored.

Technical view

CVE-2025-40013 affects Linux ASoC Qualcomm audioreach code. audioreach_widget_load_module_common() can return NULL or an error pointer, and the vulnerable path may dereference it without a NULL check. Stable kernel commits add the missing validation. No CWE, CVSS vector, or exploitability detail is provided in the source bundle.

Likely exposure

Exposure appears limited to Linux systems using affected kernel builds with the Qualcomm ASoC audioreach driver path present or enabled. Downstream distribution kernels may have backported the stable fix, so kernel version alone is not enough to confirm vulnerability.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not claim active exploitation or public exploit availability. The practical trigger conditions are not fully described beyond topology parsing returning NULL or an error pointer.

Researcher notes

The source evidence supports a missing defensive check, not a complete exploit scenario. Research should focus on reachability of audioreach topology parsing, required privileges or inputs, and whether distro kernels carry the stable backport.

Mitigation direction

  • Apply a kernel update containing the referenced stable fix commits.
  • Check your Linux distribution advisory for backported fixes.
  • Prioritize Qualcomm audio platform systems if this driver is enabled.
  • Track vendor guidance because CVSS and impact details are incomplete.

Validation and detection

  • Inventory Linux kernel versions and downstream patch levels.
  • Check whether Qualcomm ASoC audioreach support is built or loaded.
  • Verify the applicable stable commit or vendor backport is present.
  • Review kernel logs for related NULL dereference or audio driver oops events.
Prepared
Confidence
medium
Sources
8

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-40013 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
7Source 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
LinuxLinux36ad9bf1d93d66b901342eab9f8ed6c1537655a6, 36ad9bf1d93d66b901342eab9f8ed6c1537655a6, 36ad9bf1d93d66b901342eab9f8ed6c1537655a6, 36ad9bf1d93d66b901342eab9f8ed6c1537655a6, 36ad9bf1d93d66b901342eab9f8ed6c1537655a6, 36ad9bf1d93d66b901342eab9f8ed6c1537655a6unaffected
LinuxLinux5.16, 0, 6.1.156, 6.6.110, 6.12.51, 6.16.11, 6.17.1, 6.18affected
Weakness

CWE details

No CWE listed

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