nday
CVE-2026-68132

super: fix emergency thaw deadlock on frozen block devices

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
08-10T11:58Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In the Linux kernel, the following vulnerability has been resolved:

super: fix emergency thaw deadlock on frozen block devices

do_thaw_all_callback() calls bdev_thaw() while holding sb->s_umount exclusively. If the block device was frozen via bdev_freeze() dropping the last block layer freeze reference calls fs_bdev_thaw() which reacquires s_umount:

do_thaw_all_callback(sb)
  super_lock_excl(sb)                     # holds sb->s_umount
  bdev_thaw(sb->s_bdev)
    mutex_lock(&bdev->bd_fsfreeze_mutex)
    # bd_fsfreeze_count drops 1 -> 0
    bd_holder_ops->thaw == fs_bdev_thaw
      get_bdev_super(bdev)
        bdev_super_lock(bdev, true)
          super_lock(sb, true)
            down_write(&sb->s_umount)     # same task: deadlock

The emergency thaw worker deadlocks against itself holding both s_umount and bd_fsfreeze_mutex. That fscks any subsequent unmount, freeze, or thaw of that filesystem and block device.

[   81.878470] sysrq: Show Blocked State
[   81.880140] task:kworker/0:1     state:D stack:0     pid:11    tgid:11    ppid:2      task_flags:0x4208060 flags:0x00080000
[   81.884876] Workqueue: events do_thaw_all
[   81.886656] Call Trace:
[   81.887759]  <TASK>
[   81.888763]  __schedule+0x579/0x1420
[   81.890372]  schedule+0x3a/0x100
[   81.891794]  schedule_preempt_disabled+0x15/0x30
[   81.893848]  rwsem_down_write_slowpath+0x1ea/0x900
[   81.895191]  ? __pfx_do_thaw_all_callback+0x10/0x10
[   81.896528]  down_write+0xbd/0xc0
[   81.897505]  super_lock+0x91/0x180
[   81.898457]  ? __mutex_lock+0xa99/0x1140
[   81.900748]  ? __mutex_unlock_slowpath+0x1f/0x400
[   81.902069]  bdev_super_lock+0x5b/0x150
[   81.903132]  get_bdev_super+0x10/0x60
[   81.904042]  fs_bdev_thaw+0x23/0xf0
[   81.904755]  bdev_thaw+0x82/0x100
[   81.905484]  do_thaw_all_callback+0x2c/0x50
[   81.906298]  __iterate_supers+0x5d/0x130
[   81.907067]  do_thaw_all+0x20/0x40
[   81.907739]  process_one_work+0x206/0x5e0
[   81.908545]  worker_thread+0x1e2/0x3c0
[   81.909339]  ? __pfx_worker_thread+0x10/0x10
[   81.910171]  kthread+0xf4/0x130
[   81.910799]  ? __pfx_kthread+0x10/0x10
[   81.911528]  ret_from_fork+0x2e2/0x3b0
[   81.912259]  ? __pfx_kthread+0x10/0x10
[   81.913010]  ret_from_fork_asm+0x1a/0x30
[   81.913806]  </TASK>

bdev_super_lock() even documents the violated requirement with lockdep_assert_not_held(&sb->s_umount).

Acquiring bd_fsfreeze_mutex under s_umount also inverts the bd_fsfreeze_mutex vs. s_umount ordering established by bdev_{freeze,thaw}() and can thus ABBA against a concurrent block-layer freeze even when the recursive path isn't hit.

Fix this by not holding s_umount around the bdev_thaw() loop at all. Pin the superblock with an active reference instead as filesystems_freeze_callback() does. The active reference keeps the superblock from being shut down and so ->s_bdev stays valid without holding s_umount. The block-layer-held freeze is dropped by fs_bdev_thaw() with FREEZE_MAY_NEST | FREEZE_HOLDER_USERSPACE exactly as a regular unfreeze would and thaw_super_locked() handles filesystem-level freezes as before.

The emergency thaw path has deadlocked like this in one form or another for a long long time but the current exclusively-held shape dates back to commit [1] where thaw_bdev() already ended in thaw_super() with s_umount held by do_thaw_all_callback().

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , bulk import · raw
{
  "id": 13074,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-68132",
  "occurred_at": "2026-08-10T11:58:55.196Z",
  "observed_at": "2026-11-12T14:10:31.286634Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "ssvc": {
      "timestamp": "2026-11-06T16:42:51.650139Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2026-08-10T11:58:55.196Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.