Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38706, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 50cd9b5317d5593d0a33f4227f56ddcc1bf66604 – < 8b465bedc2b417fd27c1d1ab7122882b4b60b1a0
    • affected 50cd9b5317d5593d0a33f4227f56ddcc1bf66604 – < 82ba7b8cf9f6e3bf392a9f08ba3d1c0b200ccb94
    • affected 50cd9b5317d5593d0a33f4227f56ddcc1bf66604 – < 7f8fc03712194fd4e2df28af7f7f7a38205934ef
    • affected 50cd9b5317d5593d0a33f4227f56ddcc1bf66604 – < 41f53afe53a57a7c50323f99424b598190acf192
    • affected 50cd9b5317d5593d0a33f4227f56ddcc1bf66604 – < 2fce20decc6a83f16dd73744150c4e7ea6c97c21
    • affected 50cd9b5317d5593d0a33f4227f56ddcc1bf66604 – < cecc65827ef3df9754e097582d89569139e6cd1e
    • affected 50cd9b5317d5593d0a33f4227f56ddcc1bf66604 – < 7ce0a7255ce97ed7c54afae83fdbce712a1f0c9e
    • affected 50cd9b5317d5593d0a33f4227f56ddcc1bf66604 – < 2d91cb261cac6d885954b8f5da28b5c176c18131
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.241 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.149 – ≤ 6.1.*
    • unaffected 6.6.103 – ≤ 6.6.*
    • unaffected 6.12.43 – ≤ 6.12.*
    • unaffected 6.15.11 – ≤ 6.15.*
    • unaffected 6.16.2 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38706 badge
[![CVE-2025-38706](https://cveledger.app/badge/CVE-2025-38706.svg)](https://cveledger.app/cve/CVE-2025-38706)

Record last updated .