Към съдържанието
Търсене

CVE-2026-52977: Linux

Няма оценка

CVSS

Няма данни

Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)

Няма потвърждение

Атакува се

Няма данни

Време до експлоатация

    Описание

    Оригинално описание

    In the Linux kernel, the following vulnerability has been resolved: futex: Prevent lockup in requeue-PI during signal/ timeout wakeup During wait-requeue-pi (task A) and requeue-PI (task B) the following race can happen: Task A Task B futex_wait_requeue_pi() futex_setup_timer() futex_do_wait() futex_requeue() CLASS(hb, hb1)(&key1); CLASS(hb, hb2)(&key2); *timeout* futex_requeue_pi_wakeup_sync() requeue_state = Q_REQUEUE_PI_IGNORE *blocks on hb->lock* futex_proxy_trylock_atomic() futex_requeue_pi_prepare() Q_REQUEUE_PI_IGNORE => -EAGAIN double_unlock_hb(hb1, hb2) *retry* Task B acquires both hb locks and attempts to acquire the PI-lock of the top most waiter (task B). Task A is leaving early due to a signal/ timeout and started removing itself from the queue. It updates its requeue_state but can not remove it from the list because this requires the hb lock which is owned by task B. Usually task A is able to swoop the lock after task B unlocked it. However if task B is of higher priority then task A may not be able to wake up in time and acquire the lock before task B gets it again. Especially on a UP system where A is never scheduled. As a result task A blocks on the lock and task B busy loops, trying to make progress but live locks the system instead. Tragic. This can be fixed by removing the top most waiter from the list in this case. This allows task B to grab the next top waiter (if any) in the next iteration and make progress. Remove the top most waiter if futex_requeue_pi_prepare() fails. Let the waiter conditionally remove itself from the list in handle_early_requeue_p

    Засегнати продукти

    • Linux Linux: 07d91ef510fb16a2e0ca7453222105835b7ba3b8 преди e5dbae3572757cecc3d3ec7cf96cbcc9cd9f016c; 07d91ef510fb16a2e0ca7453222105835b7ba3b8 преди 4e0ed44e51727d56244a822ab941efe507c47966; 07d91ef510fb16a2e0ca7453222105835b7ba3b8 преди e3f95b1ba242e37093305812df7fdbe7288a43ac; 07d91ef510fb16a2e0ca7453222105835b7ba3b8 преди 0aacb6d18f76552e3e0ee25d9f40d21b3486f4cf; 07d91ef510fb16a2e0ca7453222105835b7ba3b8 преди 69a7cfc66405aeaa2483147653d031b3592ffc9c; 07d91ef510fb16a2e0ca7453222105835b7ba3b8 преди 0304d60abb9dcc02bc7fe6d1850f4ca206e8f1a0; 07d91ef510fb16a2e0ca7453222105835b7ba3b8 преди bc7304f3ae20972d11db6e0b1b541c63feda5f05
    • Linux Linux: 5.15; преди 5.15; 5.15.216 до 5.15.*; 6.1.175 до 6.1.*; 6.6.141 до 6.6.*; 6.12.91 до 6.12.*; 6.18.33 до 6.18.*; 7.0.10 до 7.0.*; от 7.1 нататък

    История

    • 24 юни 2026 Публикувано

    Други уязвимости в Linux Linux

    Първоизточници

    CVE-2026-52977: Linux | freedomonline.bg