VulnerabilityPublished 3 Jul 2025Updated 5 Nov 2026

CVE-2025-38105: Linux kernel · ALSA: usb-audio: Kill timer properly at removal

Affects Linux kernelSource CVE Database V5

Compare

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

Data as of 5 Nov 2026, 21:04 UTC

Severity

Unrated

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

Thin evidence

One scorer or none

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 efaf61052b8ff9ee8968912fbaf02c2847c78ede, c611b9e55174e439dcd85a72969b43a95f3827a4, 62066758d2ae169278e5d6aea5995b1b6f6ddeb5 +3

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ c88469704d63787e8d44ca5ea1c1bd0adc29572d, < efaf61052b8ff9ee8968912fbaf02c2847c78ede	Fixed in efaf61052b8ff9ee8968912fbaf02c2847c78ede
LinuxLinux	Affected ≥ c88469704d63787e8d44ca5ea1c1bd0adc29572d, < c611b9e55174e439dcd85a72969b43a95f3827a4	Fixed in c611b9e55174e439dcd85a72969b43a95f3827a4
LinuxLinux	Affected ≥ c88469704d63787e8d44ca5ea1c1bd0adc29572d, < 62066758d2ae169278e5d6aea5995b1b6f6ddeb5	Fixed in 62066758d2ae169278e5d6aea5995b1b6f6ddeb5
LinuxLinux	Affected ≥ c88469704d63787e8d44ca5ea1c1bd0adc29572d, < 647410a7da46067953a53c0d03f8680eff570959	Fixed in 647410a7da46067953a53c0d03f8680eff570959
LinuxLinux	Affected ≥ c88469704d63787e8d44ca5ea1c1bd0adc29572d, < 06513dd6d32c37d0364db8488cfdf3e14da238a8	Fixed in 06513dd6d32c37d0364db8488cfdf3e14da238a8
LinuxLinux	Affected ≥ c88469704d63787e8d44ca5ea1c1bd0adc29572d, < 0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1	Fixed in 0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Kill timer properly at removal The USB-audio MIDI code initializes the timer, but in a rare case, the driver might be freed without the disconnect call. This leaves the timer in an active state while the assigned object is released via snd_usbmidi_free(), which ends up with a kernel warning when the debug configuration is enabled, as spotted by fuzzer. For avoiding the problem, put timer_shutdown_sync() at snd_usbmidi_free(), so that the timer can be killed properly. While we're at it, replace the existing timer_delete_sync() at the disconnect callback with timer_shutdown_sync(), too.

References

Community reviews

Loading reviews…