CVE-2026-68173

Local data corruption and hangs via stale completion

Published Aug 10, 2026 · Updated Aug 10, 2026

Race condition in the ublk recovery path in Linux allows local users to corrupt data and hang block I/O during daemon recovery. END_USER_RECOVERY can consume a stale ub->completion, mark the device LIVE before queue cancellation clears, and strand a requeued request while it holds a tag. Control of a user-recoverable ublk server is required; a stranded flush request can break PREFLUSH ordering, block later fsync calls indefinitely, and hang teardown.

CVSS severity7.1
High
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Race condition in the ublk recovery path in Linux allows local users to corrupt data and hang block I/O during daemon recovery. END_USER_RECOVERY can consume a stale ub->completion, mark the device LIVE before queue cancellation clears, and strand a requeued request while it holds a tag. Control of a user-recoverable ublk server is required; a stranded flush request can break PREFLUSH ordering, block later fsync calls indefinitely, and hang teardown.

The record

CVE
CVE-2026-68173
Published
Aug 10, 2026
Updated
Aug 10, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 10, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 10, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=42ea64e01c96e594fb4f80c54dfe4f934d008a6e
  2. Affected versionversion=6.14.6 <6.15
  3. Affected versionversion=6.15
  4. Affected versionversion=728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b <432a9b2780c0a01caf547bd1fc2fcf28aeb8d173
  5. Affected versionversion=728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b <7dd26adf7e7d482af524e3a0cca4a81ef7c159d0
  6. Affected versionversion=728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b <8f188dd11a1c2ad94caeaee36ef68bb8221d4a12

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=42ea64e01c96e594fb4f80c54dfe4f934d008a6e; version=6.14.6 <6.15; version=6.15; version=728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b <432a9b2780c0a01caf547bd1fc2fcf28aeb8d173; version=728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b <7dd26adf7e7d482af524e3a0cca4a81ef7c159d0; version=728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b <8f188dd11a1c2ad94caeaee36ef68bb8221d4a12

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499.004Endpoint Denial of Service: Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo