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-39997ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free The previous commit 0718a78f6a9f ("ALSA: usb-audio: Kill timer properly at removal") patched a UAF issue caused by the error timer. However, because the error timer kill added in this patch occurs after the endpoint delete, a race condition to UAF still occurs, albeit rarely. Additionally, since kill-cleanup for urb is also missing, freed memory can be accessed in interrupt context related to urb, which can cause UAF. Therefore, to prevent this, error timer and urb must be killed before freeing the heap memory.

Timeline

  1. ID reserved

    By Linux

  2. · 6 months later

    Published

  3. · 12 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 06513dd6d32c37d0364db8488cfdf3e14da238a8 – < e63f049c7764b615d1d50cb486745fa63372b42d
    • affected efaf61052b8ff9ee8968912fbaf02c2847c78ede – < e16985513e89466a236d2a7c202783b4dd0c5a46
    • affected 647410a7da46067953a53c0d03f8680eff570959 – < dc4874366cf6cf4a31d8fa4b7f0e2a5b2d7647ba
    • affected c611b9e55174e439dcd85a72969b43a95f3827a4 – < 647d6b8d22be12842fde6ed0c56859ebc615f21e
    • affected 0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1 – < af600e7f5526d16146b3ae99f6ad57bfea79ca33
    • affected 0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1 – < 353d8c715cc951a980728133c9dd64ca5a0a186c
    • affected 0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1 – < 9f2c0ac1423d5f267e7f1d1940780fc764b0fee3
    • affected 62066758d2ae169278e5d6aea5995b1b6f6ddeb5
    • affected 6.1.167 – < 6.1.175
    • affected 6.15.3 – < 6.16
  • Linux · Linux

    • affected 6.16
    • unaffected < 6.16
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.16.11 – ≤ 6.16.*
    • unaffected 6.17.1 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .