GHSA-5F39-WJPQ-XRRJ

Vulnerability from github – Published: 2026-06-25 09:31 – Updated: 2026-06-25 09:31
VLAI
Details

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

futex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-deadlock

When FUTEX_CMP_REQUEUE_PI requeues a non-top waiter that already owns the target PI futex, task_blocks_on_rt_mutex() returns -EDEADLK before setting waiter->task.

The subsequent remove_waiter() in rt_mutex_start_proxy_lock() dereferences the NULL waiter->task, causing a kernel crash.

Add a self-deadlock check for non-top waiters before calling rt_mutex_start_proxy_lock(), analogous to the top-waiter check in futex_lock_pi_atomic().

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-53166"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-06-25T09:16:33Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfutex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-deadlock\n\nWhen FUTEX_CMP_REQUEUE_PI requeues a non-top waiter that already owns the\ntarget PI futex, task_blocks_on_rt_mutex() returns -EDEADLK before setting\nwaiter-\u003etask.\n\nThe subsequent remove_waiter() in rt_mutex_start_proxy_lock() dereferences\nthe NULL waiter-\u003etask, causing a kernel crash.\n\nAdd a self-deadlock check for non-top waiters before calling\nrt_mutex_start_proxy_lock(), analogous to the top-waiter check in\nfutex_lock_pi_atomic().",
  "id": "GHSA-5f39-wjpq-xrrj",
  "modified": "2026-06-25T09:31:19Z",
  "published": "2026-06-25T09:31:19Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-53166"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/16f8e17184b31382076f84751db5ac51fc02733e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1f2f3f3eacd6653ab215c5d2ea70811148d433fc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/74e144274af39935b0f410c0ee4d2b91c3730414"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…