[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2025-39977":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T14:53:31.930Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":21,"related":22,"reserved_at":9,"published_at":23,"modified_at":24,"state":9,"summary":25,"references_raw":27,"kevs":34,"epss":9,"epss_history":35,"metrics":36,"affected":37},"DEBIAN-CVE-2025-39977","In the Linux kernel, the following vulnerability has been resolved:  futex: Prevent use-after-free during requeue-PI  syzbot managed to trigger the following race:     T1                               T2   futex_wait_requeue_pi()    futex_do_wait()      schedule()                                futex_requeue()                                  futex_proxy_trylock_atomic()                                    futex_requeue_pi_prepare()                                    requeue_pi_wake_futex()                                      futex_requeue_pi_complete()                                       /* preempt */           * timeout/ signal wakes T1 *     futex_requeue_pi_wakeup_sync() // Q_REQUEUE_PI_LOCKED    futex_hash_put()   // back to userland, on stack futex_q is garbage                                        /* back */                                      wake_up_state(q->task, TASK_NORMAL);  In this scenario futex_wait_requeue_pi() is able to leave without using futex_q::lock_ptr for synchronization.  This can be prevented by reading futex_q::task before updating the futex_q::requeue_state. A reference on the task_struct is not needed because requeue_pi_wake_futex() is invoked with a spinlock_t held which implies a RCU read section.  Even if T1 terminates immediately after, the task_struct will remain valid during T2's wake_up_state().  A READ_ONCE on futex_q::task before futex_requeue_pi_complete() is enough because it ensures that the variable is read before the state is updated.  Read futex_q::task before updating the requeue state, use it for the following wakeup.",null,[],[],[],[14],{"_key":15},"CVE-2025-39977",[17,19],{"_key":18},"DLA-4379-1",{"_key":20},"DSA-6053-1",[],[],"2025-10-15T08:15:35.517Z","2026-04-28T20:30:24.828247Z",{"cisa_kev":26,"cisa_ransomware":26,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[28],{"url":29,"sources":30,"tags":32},"https://security-tracker.debian.org/tracker/CVE-2025-39977",[31],"osv_debian",[33],"Advisory",[],[],[],[38,56],{"ecosystem":39,"name":40,"vendor":41,"product":40,"cpe_part":9,"purl_type":42,"purl_namespace":41,"purl_name":40,"source":9,"versions":43},"Debian","linux","debian","deb",[44,50,53],{"version":45,"is_range":46,"range_type":47,"version_start":9,"version_start_type":9,"version_end":48,"version_end_type":49,"fixed_in":9},"lt6_1_158_1",true,"ecosystem","6.1.158-1","excluding",{"version":51,"is_range":46,"range_type":47,"version_start":9,"version_start_type":9,"version_end":52,"version_end_type":49,"fixed_in":9},"lt6_12_57_1","6.12.57-1",{"version":54,"is_range":46,"range_type":47,"version_start":9,"version_start_type":9,"version_end":55,"version_end_type":49,"fixed_in":9},"lt6_16_10_1","6.16.10-1",{"ecosystem":39,"name":57,"vendor":41,"product":57,"cpe_part":9,"purl_type":42,"purl_namespace":41,"purl_name":57,"source":9,"versions":58},"linux-6.1",[59],{"version":60,"is_range":46,"range_type":47,"version_start":9,"version_start_type":9,"version_end":61,"version_end_type":49,"fixed_in":9},"lt6_1_158_1~deb11u1","6.1.158-1~deb11u1"]