---
id: CVE-2026-64425
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item

  commit 10dc95939817 ("io_uring/io-wq: check IO_WQ_BIT_EXIT inside work
  run loop") fixed the obvious c…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item

  commit 10dc95939817 ("io_uring/io-wq: check IO_WQ_BIT_EXIT inside work
  run loop") fixed the obvious c…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 5.10.253, < 5.10.261'
  - 'linux_kernel >= 5.15.203, < 5.15.212'
  - 'linux_kernel >= 6.1.167, < 6.1.178'
  - 'linux_kernel >= 6.6.122, < 6.6.145'
  - 'linux_kernel >= 6.12.68, < 6.12.96'
  - 'linux_kernel >= 6.18.8, < 6.18.39'
  - 'linux_kernel >= 6.19.1, < 7.1.4'
  - linux_kernel = 6.19
patched:
  - linux_kernel 7.1.4
published: '2026-07-25'
updated: '2026-09-08'
sourceUpdated: '2026-09-08T09:18:19.647'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-64425'
references:
  - url: 'https://git.kernel.org/stable/c/14b7ecad2ec56699325180a744f4b19f046401bb'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/1636d85dc139b07c0449308f2bb5e0c7a2e0da99'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/29bef9934b2521f787bb15dd1985d4c0d12ae02a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6e2f51f3e06773c2ee98ad09738f0908b48f76f9'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ab85765cbe3258b43dc6729af0e6ce3a87a133d8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/b6f179a653a934736c88d820fe0098c3c2532549'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d179533c610e1b4c6aa436e3c1fd1b719d2c727c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ea61b04e1d7242cb37f5ed2cc91cf21a493f6597'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-019113.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.00166
epssPercentile: 0.05211
ingestedAt: '2026-09-08T15:33:26.949Z'
---

## Overview

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

io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item

commit 10dc95939817 ("io_uring/io-wq: check IO_WQ_BIT_EXIT inside work
run loop") fixed the obvious case where io_worker_handle_work() took one
exit-bit snapshot before draining pending work, but the fix stops one
level too early.

io_worker_handle_work() now re-checks IO_WQ_BIT_EXIT in its outer work
run loop, yet it still snapshots that bit once before processing a whole
dependent linked-work chain. If io_wq_exit_start() sets IO_WQ_BIT_EXIT
after the first linked item has started, the remaining linked items can
still reuse stale do_kill = false, skip IO_WQ_WORK_CANCEL, and continue
running after exit has begun.

Move the check further inside, so it covers linked items too. Note: this
is a syzbot special as it loves setting up tons of slow linked work on
weird devices like msr that take forever to read, and immediately close
the ring. Exit then takes a long time.

## Affected

- `linux_kernel >= 5.10.253, < 5.10.261`
- `linux_kernel >= 5.15.203, < 5.15.212`
- `linux_kernel >= 6.1.167, < 6.1.178`
- `linux_kernel >= 6.6.122, < 6.6.145`
- `linux_kernel >= 6.12.68, < 6.12.96`
- `linux_kernel >= 6.18.8, < 6.18.39`
- `linux_kernel >= 6.19.1, < 7.1.4`
- `linux_kernel = 6.19`

## Remediation

Upgrade past the affected range:

- `linux_kernel 7.1.4`