CVE-2025-39997
Last modified
CVE-2025-39997 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 06513dd6d32c37d0364db8488cfdf3e14da238a8, < e63f049c7764b615d1d50cb486745fa63372b42d; >= efaf61052b8ff9ee8968912fbaf02c2847c78ede, < e16985513e89466a236d2a7c202783b4dd0c5a46; >= 647410a7da46067953a53c0d03f8680eff570959, < dc4874366cf6cf4a31d8fa4b7f0e2a5b2d7647ba; >= c611b9e55174e439dcd85a72969b43a95f3827a4, < 647d6b8d22be12842fde6ed0c56859ebc615f21e; >= 0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1, < af600e7f5526d16146b3ae99f6ad57bfea79ca33; >= 0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1, < 353d8c715cc951a980728133c9dd64ca5a0a186c; >= 0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1, < 9f2c0ac1423d5f267e7f1d1940780fc764b0fee3; 62066758d2ae169278e5d6aea5995b1b6f6ddeb5; >= 6.1.167, < 6.1.175; >= 6.15.3, < 6.16 |
| Linux | Linux | 6.16 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-39997?
How severe is CVE-2025-39997?
How do I fix CVE-2025-39997?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-39991In the Linux kernel, the following vulnerability has been re…
- CVE-2025-39992In the Linux kernel, the following vulnerability has been re…
- CVE-2025-39993In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39994In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2025-39995In the Linux kernel, the following vulnerability has been re…
- CVE-2025-39996In the Linux kernel, the following vulnerability has been re…
- CVE-2025-39998In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-39999In the Linux kernel, the following vulnerability has been re…
- CVE-2025-4000A vulnerability, which was classified as problematic, was fo…5.4
- CVE-2025-40000In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2025-40001In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40002In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2025-39997?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
