Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 3 weeks ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
futex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-deadlock

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().

Affected products

Linux
  • <1f2f3f3eacd6653ab215c5d2ea70811148d433fc
  • <6.2
  • ==8a1fc8d698ac5e5916e3082a0f74450d71f9611f
  • <6.7
  • <74e144274af39935b0f410c0ee4d2b91c3730414
  • <16f8e17184b31382076f84751db5ac51fc02733e
  • <6.13
  • ==6d52dfcb2a5db86e346cf51f8fcf2071b8085166
  • <7.0.13
  • <6.18.36
  • ==d8cce4773c2b23d819baf5abedc62f7b430e8745