# CVE-2026-99262: io_uring/timeout: don't lose a cancel as io-wq arms a timeout

Status: published. Published: 2026-11-03. Updated: 2026-11-03.

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

io_uring/timeout: don't lose a cancel as io-wq arms a timeout

An IORING_OP_TIMEOUT run by io-wq, because of IOSQE_ASYNC, has the same
problem as poll, futex and waitid. io_wq_submit_work() looks at
IO_WQ_WORK_CANCEL once, before it issues the request. A cancel in between
flags the work, gets -EALREADY, and searches ->timeout_list in vain,
while the worker then adds the request and starts the timer:

  io-wq worker                          io_try_cancel()
  io_wq_submit_work()
    IO_WQ_WORK_CANCEL isn't set
                                        io_async_cancel_one()
                                          sets IO_WQ_WORK_CANCEL
                                          = -EALREADY
                                        io_timeout_cancel() = -ENOENT
    io_timeout()
      adds the request to ->timeout_list
      hrtimer_start()
    = IOU_ISSUE_SKIP_COMPLETE

Nobody looks at the flag again, and the timeout runs its course. At ring
exit, io_uring_try_cancel_requests() cancels io-wq work and then kills
the timeouts the same way, so an exiting task can get stuck for the full
duration of such a timeout.

Look at the flag under ->timeout_lock, which the search takes as well,
and fail the request if it is set. If the search came first, the flag is
visible. If it comes later, it finds the request on the list.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ ce35a47a3a0208a77b4d31b7f2e8ed57d624093d; < f1fabf17f37b252b11d8fe5c70c8056b70b005ca (affected, git); ≥ ce35a47a3a0208a77b4d31b7f2e8ed57d624093d; < 68cd06ba918d9658c36c1973a0184795738dcc46 (affected, git); ≥ ce35a47a3a0208a77b4d31b7f2e8ed57d624093d; < f9d5e02649587885852f46b6dc7c081b87f0ac3a (affected, git); ≥ ce35a47a3a0208a77b4d31b7f2e8ed57d624093d; < f10ab47077e63d6eee35b242c257c3947bb49e64 (affected, git); ≥ ce35a47a3a0208a77b4d31b7f2e8ed57d624093d; < df705a274da10da7bb546e08b49fa80a6ef19c78 (affected, git). Source: CNA: Linux
- Linux / Linux: 5.6 (affected); ≥ 0; < 5.6 (unaffected, semver); ≥ 6.1.191; ≤ 6.1.* (unaffected, semver); ≥ 6.6.161; ≤ 6.6.* (unaffected, semver); ≥ 6.12.115; ≤ 6.12.* (unaffected, semver); ≥ 6.18.60; ≤ 6.18.* (unaffected, semver); ≥ 7.2.14; ≤ 7.2.* (unaffected, semver). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/f1fabf17f37b252b11d8fe5c70c8056b70b005ca (CNA: Linux)

- https://git.kernel.org/stable/c/68cd06ba918d9658c36c1973a0184795738dcc46 (CNA: Linux)

- https://git.kernel.org/stable/c/f9d5e02649587885852f46b6dc7c081b87f0ac3a (CNA: Linux)

- https://git.kernel.org/stable/c/f10ab47077e63d6eee35b242c257c3947bb49e64 (CNA: Linux)

- https://git.kernel.org/stable/c/df705a274da10da7bb546e08b49fa80a6ef19c78 (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99262; retrieved 2026-11-03; source updated 2026-11-03

Revision: 52f3cb3557fea2f64172bb79bc9d6614368b530f1bd2bb13778fcb6423238a6e

Canonical: https://y2.dev/cve/CVE-2026-99262

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.