Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-37805: sound/virtio: Fix cancel_sync warnings on uninitialized work_structs

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3c7df2e27346eb40a0e86230db1ccab195c97cfe, 54c7b864fbe4423a07b443a4ada0106052942116, 5be9407b41eae20eef9140f5cfbfcbc3d01aaf45; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.

Low priority for now. Upgrade to Linux Linux 3c7df2e27346eb40a0e86230db1ccab195c97cfe, 54c7b864fbe4423a07b443a4ada0106052942116, 5be9407b41eae20eef9140f5cfbfcbc3d01aaf45; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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!

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 8, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-37805

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 5.15.181
  • linux linux kernel5.16 and later · before 6.1.136
  • linux linux kernel6.2 and later · before 6.6.89
  • linux linux kernel6.7 and later · before 6.12.26
  • linux linux kernel6.13 and later · before 6.14.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.13affected
    • 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2 and later · before e03b10c45c7675b6098190c6e7de1b656d8bcdbeaffected · git
    • 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2 and later · before 54c7b864fbe4423a07b443a4ada0106052942116affected · git
    • 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2 and later · before 5be9407b41eae20eef9140f5cfbfcbc3d01aaf45affected · git
    • 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2 and later · before 66046b586c0aaa9332483bcdbd76e3305d6138e9affected · git
    • 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2 and later · before 9908498ce929a5a052b79bb7942f9ea317312ce4affected · git
    • 29b96bf50ba958eb5f097cdc3fbd4c1acf9547a2 and later · before 3c7df2e27346eb40a0e86230db1ccab195c97cfeaffected · git
    • before 5.13not affected · semver
    • 5.15.181 and later · up to and including 5.15.*not affected · semver
    • 6.1.136 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.137-16.1.137-1
Debian:13linuxbefore 6.12.27-16.12.27-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-37802May 8, 2025 · ksmbd: fix WARNING "do not call blocking ops when !TASK_RUNNING"
    22Monitor
  • ← EarlierCVE-2025-37803May 8, 2025 · udmabuf: fix a buf size overflow issue during udmabuf creation
    31Monitor
  • Later →CVE-2025-37810May 8, 2025 · usb: dwc3: gadget: check that event count does not exceed event buffer length
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3c7df2e27346eb40a0e86230db1ccab195c97cfeVendor (CNA)
Linux Linux54c7b864fbe4423a07b443a4ada0106052942116Vendor (CNA)
Linux Linux5be9407b41eae20eef9140f5cfbfcbc3d01aaf45Vendor (CNA)
Linux Linux66046b586c0aaa9332483bcdbd76e3305d6138e9Vendor (CNA)
Linux Linux9908498ce929a5a052b79bb7942f9ea317312ce4Vendor (CNA)
Linux Linuxe03b10c45c7675b6098190c6e7de1b656d8bcdbeVendor (CNA)
azl3 kernel 6.6.85.1-4 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.92.2-1 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.137-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2021-47137409 days apartnet: lantiq: fix memory corruption in RX ring
    39Monitor
  • CVE-2024-35969353 days apartipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr
    35Monitor
  • CVE-2024-34027318 days apartf2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock
    31Monitor
  • CVE-2021-47551349 days apartdrm/amd/amdkfd: Fix kernel panic when reset failed and been triggered again
    31Monitor
  • CVE-2021-47130419 days apartnvmet: fix freeing unallocated p2pmem
    30Monitor
  • CVE-2024-26894386 days apartACPI: processor_idle: Fix memory leak in acpi_processor_power_exit()
    24Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records