Skip to main content
VulnerabilityPublished Updated

CVE-2025-38706: Linux kernel · ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in cecc65827ef3df9754e097582d89569139e6cd1e : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in cecc65827ef3df9754e097582d89569139e6cd1e, 82ba7b8cf9f6e3bf392a9f08ba3d1c0b200ccb94, 41f53afe53a57a7c50323f99424b598190acf192 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 50cd9b5317d5593d0a33f4227f56ddcc1bf66604, < cecc65827ef3df9754e097582d89569139e6cd1e
Fixed in
  • cecc65827ef3df9754e097582d89569139e6cd1e
LinuxLinuxAffected
  • ≥ 50cd9b5317d5593d0a33f4227f56ddcc1bf66604, < 82ba7b8cf9f6e3bf392a9f08ba3d1c0b200ccb94
Fixed in
  • 82ba7b8cf9f6e3bf392a9f08ba3d1c0b200ccb94
LinuxLinuxAffected
  • ≥ 50cd9b5317d5593d0a33f4227f56ddcc1bf66604, < 41f53afe53a57a7c50323f99424b598190acf192
Fixed in
  • 41f53afe53a57a7c50323f99424b598190acf192
LinuxLinuxAffected
  • ≥ 50cd9b5317d5593d0a33f4227f56ddcc1bf66604, < 8b465bedc2b417fd27c1d1ab7122882b4b60b1a0
Fixed in
  • 8b465bedc2b417fd27c1d1ab7122882b4b60b1a0
LinuxLinuxAffected
  • ≥ 50cd9b5317d5593d0a33f4227f56ddcc1bf66604, < 7f8fc03712194fd4e2df28af7f7f7a38205934ef
Fixed in
  • 7f8fc03712194fd4e2df28af7f7f7a38205934ef
LinuxLinuxAffected
  • ≥ 50cd9b5317d5593d0a33f4227f56ddcc1bf66604, < 7ce0a7255ce97ed7c54afae83fdbce712a1f0c9e
Fixed in
  • 7ce0a7255ce97ed7c54afae83fdbce712a1f0c9e

Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() snd_soc_remove_pcm_runtime() might be called with rtd == NULL which will leads to null pointer dereference. This was reproduced with topology loading and marking a link as ignore due to missing hardware component on the system. On module removal the soc_tplg_remove_link() would call snd_soc_remove_pcm_runtime() with rtd == NULL since the link was ignored, no runtime was created.

References

Community reviews

Loading reviews…