همهٔ گزارش‌ها
متوسط

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

A flaw was found in the Linux kernel's futex (Fast Userspace Mutex) requeue mechanism. When a non-top waiter attempts to requeue a Priority Inheritance (PI) futex it already owns, a NULL pointer dereference can occur. This issue, specifically within the remove_waiter() function during a self-deadlock scenario, leads to a kernel crash, resulting in a Denial of Service (DoS).