Vulnerability · Published Jan 13, 2026 · Assigned by Linux

CVE-2025-68807block: fix race between wbt_enable_default and IO submission

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 8% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 91.7% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: block: fix race between wbt_enable_default and IO submission When wbt_enable_default() is moved out of queue freezing in elevator_change(), it can cause the wbt inflight counter to become negative (-1), leading to hung tasks in the writeback path. Tasks get stuck in wbt_wait() because the counter is in an inconsistent state. The issue occurs because wbt_enable_default() could race with IO submission, allowing the counter to be decremented before proper initialization. This manifests as: rq_wait[0]: inflight: -1 has_waiters: True rwb_enabled() checks the state, which can be updated exactly between wbt_wait() (rq_qos_throttle()) and wbt_track()(rq_qos_track()), then the inflight counter will become negative. And results in hung task warnings like: task:kworker/u24:39 state:D stack:0 pid:14767 Call Trace: rq_qos_wait+0xb4/0x150 wbt_wait+0xa9/0x100 __rq_qos_throttle+0x24/0x40 blk_mq_submit_bio+0x672/0x7b0 ... Fix this by: 1. Splitting wbt_enable_default() into: - __wbt_enable_default(): Returns true if wbt_init() should be called - wbt_enable_default(): Wrapper for existing callers (no init) - wbt_init_enable_default(): New function that checks and inits WBT 2. Using wbt_init_enable_default() in blk_register_queue() to ensure proper initialization during queue registration 3. Move wbt_init() out of wbt_enable_default() which is only for enabling disabled wbt from bfq and iocost, and wbt_init() isn't needed. Then the original lock warning can be avoided. 4. Removing the ELEVATOR_FLAG_ENABLE_WBT_ON_EXIT flag and its handling code since it's no longer needed This ensures WBT is properly initialized before any IO can be submitted, preventing the counter from going negative.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux6.18.3-1DEBIAN-CVE-2025-68807
Ubuntu:25.10linux6.17.0-22.22USN-8177-1
Ubuntu:25.10linux6.17.0-22.22UBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-68807
Ubuntu:25.10linux-aws6.17.0-1012.12UBUNTU-CVE-2025-68807
Ubuntu:25.10linux-aws6.17.0-1012.12USN-8183-2
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1012.12~24.04.1UBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1012.12~24.04.1USN-8183-2
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-68807
Ubuntu:25.10linux-azure6.17.0-1013.13USN-8245-1
Ubuntu:25.10linux-azure6.17.0-1013.13UBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1013.13~24.04.1USN-8245-1
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1013.13~24.04.1UBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-68807
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-68807
Ubuntu:25.10linux-gcp6.17.0-1012.12USN-8183-1
Ubuntu:25.10linux-gcp6.17.0-1012.12UBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1012.12~24.04.1UBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1012.12~24.04.1USN-8183-1
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-22.22~24.04.1UBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-22.22~24.04.1USN-8183-2
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1018.18UBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1020.20USN-8245-1
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1020.20UBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-68807
Ubuntu:25.10linux-oracle6.17.0-1011.11USN-8183-2
Ubuntu:25.10linux-oracle6.17.0-1011.11UBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1011.11~24.04.1USN-8183-2
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1011.11~24.04.1UBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-68807
Ubuntu:25.10linux-raspi6.17.0-1013.13UBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68807
Ubuntu:25.10linux-realtime6.17.0-1010.11UBUNTU-CVE-2025-68807
Ubuntu:25.10linux-realtime6.17.0-1010.11USN-8177-1
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68807
Ubuntu:25.10linux-riscv6.17.0-22.22.1UBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-68807
Ubuntu:24.04:LTSlinux-riscv-6.176.17.0-22.22.1~24.04.1UBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-68807
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-68807

Affected products (as reported)

VendorProductVersions
Linux Linux 78c271344b6f64ce24c845e54903e09928cf2061 – before f55201fb3becff6a903fd29f4d1147cc7e91eb0c78c271344b6f64ce24c845e54903e09928cf2061 – before 9869d3a6fed381f3b98404e26e1afc75d680cbf9
Linux Linux 6.16

References