CVE-2025-68756

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-0883 (ENISA EUVD) · GHSA-p2j4-mcw8-r88g (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 5, 2026

Last Modified

October 14, 2026

Vendor Advisories for CVE-2025-68756(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(21)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-19.19) @ questing2026-11-11ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1010.10) @ questing2026-11-11ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1017.17) @ noble2026-11-11ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1054.57+fips1) @ noble2026-11-11ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9~24.04.1) @ noble2026-11-11ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-11-11ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1022.22) @ noble2026-11-11ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-11-11ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1054.57~22.04.1) @ jammy2026-11-11ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1051.54.1) @ noble2026-11-11ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2042.43) @ noble2026-11-11ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-11-11ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9) @ questing2026-11-11ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1010.10) @ questing2026-11-11ubuntu
ubuntulinux-virtual-6.8 (6.8.0-110.110) @ noble2026-11-11ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1047.48) @ noble2026-11-11ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1051.54) @ noble2026-11-11ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1049.50) @ noble2026-11-11ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1052.56) @ noble2026-11-11ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-11-11ubuntu
linuxKernel @ 6.6.120 (fixes >=6.2.0)—osv

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.63-1~bpo12+1 (8 versions)
  • every version up to 6.12.63-1: fixed in 6.12.63-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.17.9-1 (86 versions)
  • every version up to 6.17.13-1: fixed in 6.17.13-1
—

Additional Vendor Advisories

(20)

Data Freshness Timeline

(refreshed 6× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 250 rows on record for this CVE, as 99 entries (1 repeat merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 150 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-11-19 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-11-17 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-11-16 16:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-11-15 16:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-11-14 16:38 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-11-11 08:19 UTCEchelonGraph re-scored
  13. 2026-11-11 08:19 UTCVendor advisory
  14. 2026-11-11 08:19 UTCGHSA enrichmentGHSA-p2j4-mcw8-r88g
  15. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 74 more
  1. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-27 14:25 UTCOSV refresh
  6. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-25 16:04 UTCEchelonGraph re-scored
  9. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-18 05:17 UTCEchelonGraph re-scored
  17. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-14 19:40 UTCGHSA enrichmentGHSA-p2j4-mcw8-r88g
  21. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-10-12 16:47 UTCEchelonGraph re-scored
  24. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-10-11 20:21 UTCEchelonGraph re-scored
  26. 2026-10-11 18:33 UTCEchelonGraph re-scored
  27. 2026-10-11 15:08 UTCEchelonGraph re-scored
  28. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  29. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  30. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  31. 2026-10-09 00:28 UTCOSV refresh
  32. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  33. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  34. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  35. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  36. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  37. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  38. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  39. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  40. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  41. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  42. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  43. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  44. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  45. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  46. 2026-09-19 07:30 UTCOSV refresh
  47. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  48. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  49. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  50. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  51. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  52. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  53. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  54. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  55. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  56. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  57. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  58. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  59. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  60. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  61. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  62. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  63. 2026-08-31 11:04 UTCOSV refresh
  64. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  65. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  66. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  67. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  68. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  69. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  70. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  71. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  72. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  73. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  74. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile

Frequently asked(4)

What is CVE-2025-68756?
CVE-2025-68756 is a vulnerability whose severity is not yet rated; its CVE record was published on January 5, 2026. 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…
When was the CVE record for CVE-2025-68756 published?
The CVE record for CVE-2025-68756 was published on January 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2025-68756 actively exploited?
CVE-2025-68756 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
How do I remediate CVE-2025-68756?
A fix for CVE-2025-68756 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-68756 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68756

Explore →

Is Your Infrastructure Affected by CVE-2025-68756?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.