GHSA-6PV2-QW2R-8J4C
Vulnerability from github – Published: 2026-11-03 12:31 – Updated: 2026-11-03 21:32In 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.
{
"affected": [],
"aliases": [
"CVE-2026-99262"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-03T12:17:33Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/timeout: don\u0027t lose a cancel as io-wq arms a timeout\n\nAn IORING_OP_TIMEOUT run by io-wq, because of IOSQE_ASYNC, has the same\nproblem as poll, futex and waitid. io_wq_submit_work() looks at\nIO_WQ_WORK_CANCEL once, before it issues the request. A cancel in between\nflags the work, gets -EALREADY, and searches -\u003etimeout_list in vain,\nwhile the worker then adds the request and starts the timer:\n\n io-wq worker io_try_cancel()\n io_wq_submit_work()\n IO_WQ_WORK_CANCEL isn\u0027t set\n io_async_cancel_one()\n sets IO_WQ_WORK_CANCEL\n = -EALREADY\n io_timeout_cancel() = -ENOENT\n io_timeout()\n adds the request to -\u003etimeout_list\n hrtimer_start()\n = IOU_ISSUE_SKIP_COMPLETE\n\nNobody looks at the flag again, and the timeout runs its course. At ring\nexit, io_uring_try_cancel_requests() cancels io-wq work and then kills\nthe timeouts the same way, so an exiting task can get stuck for the full\nduration of such a timeout.\n\nLook at the flag under -\u003etimeout_lock, which the search takes as well,\nand fail the request if it is set. If the search came first, the flag is\nvisible. If it comes later, it finds the request on the list.",
"id": "GHSA-6pv2-qw2r-8j4c",
"modified": "2026-11-03T21:32:06Z",
"published": "2026-11-03T12:31:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99262"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/68cd06ba918d9658c36c1973a0184795738dcc46"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/89f193dc3ef462059387e9691bf6af4b1808379a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/df705a274da10da7bb546e08b49fa80a6ef19c78"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f10ab47077e63d6eee35b242c257c3947bb49e64"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f1fabf17f37b252b11d8fe5c70c8056b70b005ca"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f9d5e02649587885852f46b6dc7c081b87f0ac3a"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.