GHSA-WWG9-WJFM-V4PW

Vulnerability from github – Published: 2026-11-20 09:31 – Updated: 2026-11-20 09:31
VLAI
Details

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

io_uring/io-wq: save worker type before dropping its reference

io_wq_cancel_tw_create() inspects cb->func after calling io_worker_cancel_cb(). For an existing worker, that call can drop the last worker reference and wake io_worker_exit(). If the canceling task is preempted, the worker can be unlinked and freed by kfree_rcu() before the callback function is inspected. KASAN reports a slab-use-after-free read in this path.

Save whether the callback belongs to an unpublished continuation worker while its reference is still held, then use the saved result for the conditional free. This preserves the existing accounting and frees only the worker allocated for the canceled continuation.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99804"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-20T08:18:38Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/io-wq: save worker type before dropping its reference\n\nio_wq_cancel_tw_create() inspects cb-\u003efunc after calling\nio_worker_cancel_cb(). For an existing worker, that call can drop the\nlast worker reference and wake io_worker_exit(). If the canceling task\nis preempted, the worker can be unlinked and freed by kfree_rcu() before\nthe callback function is inspected. KASAN reports a slab-use-after-free\nread in this path.\n\nSave whether the callback belongs to an unpublished continuation worker\nwhile its reference is still held, then use the saved result for the\nconditional free. This preserves the existing accounting and frees only\nthe worker allocated for the canceled continuation.",
  "id": "GHSA-wwg9-wjfm-v4pw",
  "modified": "2026-11-20T09:31:34Z",
  "published": "2026-11-20T09:31:34Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99804"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/11239f2b509cd09d76c564b5fe262c70bad8ea3c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2efcf743664ab4a83b4fae1f152bbea1d298e73f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/37e425460b7c41687e51e3254b1eb1d799da9614"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9d7af67e5425ad08d1ab9bbf4a3ad987d7871834"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.