CVE-2025-37805: linux
Vulnerability summary
CVE-2025-37805 is a medium (CVSS 5.5) vulnerability in linux. EPSS estimates a 0.20% chance of exploitation in the next 30 days, higher than 9.7% of scored vulnerabilities.
Advisory lineage
Upstream 0 · Downstream 43 · Related 40Timeline
- 08-05-2025PublishedVulnerability first disclosed.
- 11-05-2026Last modifiedVulnerability information updated.
Description
In the Linux kernel, the following vulnerability has been resolved: sound/virtio: Fix cancel_sync warnings on uninitialized work_structs Betty reported hitting the following warning: [ 8.709131][ T221] WARNING: CPU: 2 PID: 221 at kernel/workqueue.c:4182 ... [ 8.713282][ T221] Call trace: [ 8.713365][ T221] __flush_work+0x8d0/0x914 [ 8.713468][ T221] __cancel_work_sync+0xac/0xfc [ 8.713570][ T221] cancel_work_sync+0x24/0x34 [ 8.713667][ T221] virtsnd_remove+0xa8/0xf8 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276] [ 8.713868][ T221] virtsnd_probe+0x48c/0x664 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276] [ 8.714035][ T221] virtio_dev_probe+0x28c/0x390 [ 8.714139][ T221] really_probe+0x1bc/0x4c8 ... It seems we're hitting the error path in virtsnd_probe(), which triggers a virtsnd_remove() which iterates over the substreams calling cancel_work_sync() on the elapsed_period work_struct. Looking at the code, from earlier in: virtsnd_probe()->virtsnd_build_devs()->virtsnd_pcm_parse_cfg() We set snd->nsubstreams, allocate the snd->substreams, and if we then hit an error on the info allocation or something in virtsnd_ctl_query_info() fails, we will exit without having initialized the elapsed_period work_struct. When that error path unwinds we then call virtsnd_remove() which as long as the substreams array is allocated, will iterate through calling cancel_work_sync() on the uninitialized work struct hitting this warning. Takashi Iwai suggested this fix, which initializes the substreams structure right after allocation, so that if we hit the error paths we avoid trying to cleanup uninitialized data. Note: I have not yet managed to reproduce the issue myself, so this patch has had limited testing. Feedback or thoughts would be appreciated!
CVSS metrics
4 scores · 4 sources · 1 version- OSV · UbuntuEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- OSV · DebianEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- NVDNIST5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS trend
Probability
0.20%
Chance of exploitation in the next 30 days
Percentile
10%
Versus all other CVEs
30-day change
+0.01 pp
From 0.19% on 19-09-2026
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeAffected systems
Ubuntu141 products
- linuxAll versions (No fix recorded) | < 5.15.0-144.157 | < 6.8.0-100.100
- linux-allwinner-5.19All versions (No fix recorded)
- linux-awsAll versions (No fix recorded) | < 5.15.0-1088.95 | < 6.8.0-1046.49
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Linux2 products
- linux≥ 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2, < e03b10c45c7675b6098190c6e7de1b656d8bcdbe | ≥ 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2, < 54c7b864fbe4423a07b443a4ada0106052942116 | ≥ 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2, < 5be9407b41eae20eef9140f5cfbfcbc3d01aaf45 | ≥ 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2, < 66046b586c0aaa9332483bcdbd76e3305d6138e9 | ≥ 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2, < 9908498ce929a5a052b79bb7942f9ea317312ce4 | ≥ 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2, < 3c7df2e27346eb40a0e86230db1ccab195c97cfe | 5.13
- linux_kernel< 5.15.181 | ≥ 5.16, < 6.1.136 | ≥ 6.2, < 6.6.89 | ≥ 6.7, < 6.12.26 | ≥ 6.13, < 6.14.5
Debian1 product
- linux< 6.1.137-1 | < 6.12.27-1
3 vendors · 144 products