{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-68173","id":"CVE-2026-68173","title":"ublk: wait on ublk_dev_ready() instead of ub->completion","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nublk: wait on ublk_dev_ready() instead of ub->completion\n\nub->completion is only re-armed by a successful START_USER_RECOVERY. If\nthe ublk server sends END_USER_RECOVERY without one - e.g. its START\nfailed with -EBUSY and the error was ignored - the wait is satisfied by\nthe stale completion of the previous recovery cycle, and the","descriptionLong":"In the Linux kernel, the following vulnerability has been resolved:\n\nublk: wait on ublk_dev_ready() instead of ub->completion\n\nub->completion is only re-armed by a successful START_USER_RECOVERY. If\nthe ublk server sends END_USER_RECOVERY without one - e.g. its START\nfailed with -EBUSY and the error was ignored - the wait is satisfied by\nthe stale completion of the previous recovery cycle, and the device is\nmarked LIVE and the requeue list kicked while the FETCH stream is still\nrunning and ubq->canceling is still set. The kick redispatches a\npreviously requeued request, __ublk_queue_rq_common() sees ->canceling\nand parks it again via __ublk_abort_rq(), and after the last FETCH\nclears ->canceling nothing ever kicks the requeue list again: the\nrequest is stranded there while holding its tag. If it is the flush\nmachinery's flush_rq, every subsequent fsync piles up in uninterruptible\nsleep and teardown hangs on tag draining. This matches a report of a\nlost PREFLUSH with ext4 on top of ublk after daemon crash recovery.\n\nub->completion is an edge-triggered latch used as a proxy for the level\ncondition \"every queue has fetched all I/O commands\", which can regress\n(F_BATCH's UNPREP, daemon death) and whose re-arm can be skipped. Drop\nit and wait on the real condition instead: the new helper\nublk_wait_dev_ready_and_lock() waits on ublk_dev_ready() via\nwait_var_event_interruptible(), woken from ublk_mark_io_ready(), then\nre-checks it under ub->mutex, waiting again on regression, and returns\nwith the mutex held and readiness guaranteed.\n\nReadiness becomes true in the same ub->mutex critical section that\nclears the last queue's ->canceling, so END_USER_RECOVERY marks the\ndevice LIVE and kicks the requeue list strictly after ->canceling\nclears. The wait stays interruptible, so a server whose daemon died can\nstill be signalled out. For ublk_ctrl_start_dev() this replaces the\nfail-fast -EINVAL on an F_BATCH ready->UNPREP regression with waiting\nuntil the device is ready again.","published":"2026-08-10T11:59:42.889Z","updated":"2026-11-17T07:03:28.108557456Z","reserved":"2026-07-30T09:28:09.372Z","status":"Received","rejected":false,"assigner":"Linux","metric":{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","rating":"high","source":"Linux"},"metrics":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","rating":"high","source":"Linux"},{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","rating":"high","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","rating":"high","source":"OSV"}],"rating":"high","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b","lessThan":"7dd26adf7e7d482af524e3a0cca4a81ef7c159d0","status":"affected","versionType":"git"},{"version":"728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b","lessThan":"8f188dd11a1c2ad94caeaee36ef68bb8221d4a12","status":"affected","versionType":"git"},{"version":"728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b","lessThan":"432a9b2780c0a01caf547bd1fc2fcf28aeb8d173","status":"affected","versionType":"git"},{"version":"42ea64e01c96e594fb4f80c54dfe4f934d008a6e","status":"affected","versionType":"git"},{"version":"6.14.6","lessThan":"6.15","status":"affected","versionType":"semver"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.15","status":"affected"},{"version":"0","lessThan":"6.15","status":"unaffected","versionType":"semver"},{"version":"6.18.42","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.1.6","lessThanOrEqual":"7.1.*","status":"unaffected","versionType":"semver"},{"version":"7.2","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":[],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/7dd26adf7e7d482af524e3a0cca4a81ef7c159d0","tags":["web"]},{"url":"https://git.kernel.org/stable/c/8f188dd11a1c2ad94caeaee36ef68bb8221d4a12","tags":["web"]},{"url":"https://git.kernel.org/stable/c/432a9b2780c0a01caf547bd1fc2fcf28aeb8d173","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68173.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68173","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":0.00162,"epssPercentile":0.05469,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-68173","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68173","ok":true,"note":"Received"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-68173","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-68173","ok":true,"note":"scored 2026-11-19"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}