cve.bz

CVE-2025-68756 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: block: Use RCU in blk_mq_[un]quiesce_tagset() instead of set->tag_list_lock blk_mq_{add,del}_queue_tag_set() functions add and remove queues from tagset, the functions make sure that tagset and queues are marked as shared when two or more queues are attached to the same tagset. Initially a tagset starts as unshared and when the number of added queues reaches two, blk_mq_add_queue_tag_set() marks it as shared along with all the queues attached to it. When the number of attached queues drops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and the remaining queues as unshared. Both functions need to freeze current queues in tagset before setting on unsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions hold set->tag_list_lock mutex, which makes sense as we do not want queues to be added or deleted in the process. This used to work fine until commit 98d81f0df70c ("nvme: use blk_mq_[un]quiesce_tagset") made the nvme driver quiesce tagset instead of quiscing individual queues. blk_mq_quiesce_tagset() does the job and quiesce the queues in set->tag_list while holding set->tag_list_lock also. This results in deadlock between two threads with these stacktraces: __schedule+0x47c/0xbb0 ? timerqueue_add+0x66/0xb0 schedule+0x1c/0xa0 schedule_preempt_disabled+0xa/0x10 __mutex_lock.constprop.0+0x271/0x600 blk_mq_quiesce_tagset+0x25/0xc0 nvme_dev_disable+0x9c/0x250 nvme_timeout+0x1fc/0x520 blk_mq_handle_expired+0x5c/0x90 bt_iter+0x7e/0x90 blk_mq_queue_tag_busy_iter+0x27e/0x550 ? __blk_mq_complete_request_remote+0x10/0x10 ? __blk_mq_complete_request_remote+0x10/0x10 ? __call_rcu_common.constprop.0+0x1c0/0x210 blk_mq_timeout_work+0x12d/0x170 process_one_work+0x12e/0x2d0 worker_thread+0x288/0x3a0 ? rescuer_thread+0x480/0x480 kthread+0xb8/0xe0 ? kthread_park+0x80/0x80 ret_from_fork+0x2d/0x50 ? kthread_park+0x80/0x80 ret_from_fork_asm+0x11/0x20 __schedule+0x47c/0xbb0 ? xas_find+0x161/0x1a0 schedule+0x1c/0xa0 blk_mq_freeze_queue_wait+0x3d/0x70 ? destroy_sched_domains_rcu+0x30/0x30 blk_mq_update_tag_set_shared+0x44/0x80 blk_mq_exit_queue+0x141/0x150 del_gendisk+0x25a/0x2d0 nvme_ns_remove+0xc9/0x170 nvme_remove_namespaces+0xc7/0x100 nvme_remove+0x62/0x150 pci_device_remove+0x23/0x60 device_release_driver_internal+0x159/0x200 unbind_store+0x99/0xa0 kernfs_fop_write_iter+0x112/0x1e0 vfs_write+0x2b1/0x3d0 ksys_write+0x4e/0xb0 do_syscall_64+0x5b/0x160 entry_SYSCALL_64_after_hwframe+0x4b/0x53 The top stacktrace is showing nvme_timeout() called to handle nvme command timeout. timeout handler is trying to disable the controller and as a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not to call queue callback handlers. The thread is stuck waiting for set->tag_list_lock as it tries to walk the queues in set->tag_list. The lock is held by the second thread in the bottom stack which is waiting for one of queues to be frozen. The queue usage counter will drop to zero after nvme_timeout() finishes, and this will not happen because the thread will wait for this mutex forever. Given that [un]quiescing queue is an operation that does not need to sleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking set->tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU safe list operations. Also, delete INIT_LIST_HEAD(&q->tag_set_list) in blk_mq_del_queue_tag_set() because we can not re-initialize it while the list is being traversed under RCU. The deleted queue will not be added/deleted to/from a tagset and it will be freed in blk_free_queue() after the end of RCU grace period.
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.6.120
  • Linux Linux: fixed in 6.12.63
  • Linux Linux: fixed in 6.17.13
  • Linux Linux: fixed in 6.18.2
  • Linux Linux: fixed in 6.19
  • Debian, Ubuntu, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2025-68756 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68756?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68756?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-68756 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-68756

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-68756](https://cve.bz/cve/badge/CVE-2025-68756.svg)](https://cve.bz/cve/CVE-2025-68756)

HTML:

<a href="https://cve.bz/cve/CVE-2025-68756"><img src="https://cve.bz/cve/badge/CVE-2025-68756.svg" alt="CVE-2025-68756"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.2 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.120
Linux6.126.12.63
Linux6.176.17.13
Linux6.186.18.2
Linuxlater releases6.19

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13linux6.12.63-1DEBIAN-CVE-2025-68756
Debian14linux6.17.13-1DEBIAN-CVE-2025-68756
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-68756
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-68756
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-68756
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-68756 USN-8179-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1059.65~22.04.1UBUNTU-CVE-2025-68756 USN-8440-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-68756
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1054.57~22.04.1UBUNTU-CVE-2025-68756 USN-8179-4
Ubuntu22.04:LTSlinux-hwe-6.8, linux-riscv-6.86.8.0-110.110~22.04.1UBUNTU-CVE-2025-68756 USN-8179-3
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1051.51~22.04.1UBUNTU-CVE-2025-68756 USN-8179-3
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-110.110.1~22.04.1UBUNTU-CVE-2025-68756 USN-8179-1
Ubuntu22.04:LTSlinux-nvidia-6.86.8.0-1051.54~22.04.1UBUNTU-CVE-2025-68756 USN-8185-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1049.50~22.04.1UBUNTU-CVE-2025-68756 USN-8203-1
42 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source6.18.5-1.1openSUSE-SU-2026:10039-1
openSUSETumbleweedkernel-source-longterm6.18.16-1.1openSUSE-SU-2026:10301-1
Azure Linux3kernel6.6.121.1-1AZL-73421
Alpaquita25linux-lts6.12.65-r0BELL-CVE-2025-68756
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-68756

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This deadlock requires specific timing conditions involving NVMe device timeout and namespace removal operations occurring simultaneously. Affected systems will hang and require a hard reboot to recover. The vulnerability primarily affects systems with multiple NVMe namespaces sharing a tag set under heavy I/O load with device errors.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-68756.

References

Check your stackJSON