CVSS 3.1
Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)
Атакува се
Време до експлоатация
Атакува се по мрежата, без особени условия, без вход и без действие от потребителя.
- Експлоатация: няма данни за експлоатация
- Атаката не може да се автоматизира
Описание
Оригинално описание
In the Linux kernel, the following vulnerability has been resolved: tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). Martin KaFai Lau reported use-after-free [0] in reqsk_timer_handler(). """ We are seeing a use-after-free from a bpf prog attached to trace_tcp_retransmit_synack. The program passes the req->sk to the bpf_sk_storage_get_tracing kernel helper which does check for null before using it. """ The commit 83fccfc3940c ("inet: fix potential deadlock in reqsk_queue_unlink()") added timer_pending() in reqsk_queue_unlink() not to call del_timer_sync() from reqsk_timer_handler(), but it introduced a small race window. Before the timer is called, expire_timers() calls detach_timer(timer, true) to clear timer->entry.pprev and marks it as not pending. If reqsk_queue_unlink() checks timer_pending() just after expire_timers() calls detach_timer(), TCP will miss del_timer_sync(); the reqsk timer will continue running and send multiple SYN+ACKs until it expires. The reported UAF could happen if req->sk is close()d earlier than the timer expiration, which is 63s by default. The scenario would be 1. inet_csk_complete_hashdance() calls inet_csk_reqsk_queue_drop(), but del_timer_sync() is missed 2. reqsk timer is executed and scheduled again 3. req->sk is accept()ed and reqsk_put() decrements rsk_refcnt, but reqsk timer still has another one, and inet_csk_accept() does not clear req->sk for non-TFO sockets 4. sk is close()d 5. reqsk timer is executed again, and BPF touches req->sk Let's not use timer_pending() by passing the caller context to __inet_csk_reqsk_queue_drop(). Note that reqsk timer is pinned, so the issue does not happen in most use cases. [1] [0] BUG: KFENCE: use-after-free read in bpf_sk_storage_get_tracing+0x2e/0x1b0 Use-after-free read at 0x00000000a891fb3a (in kfence-#1): bpf_sk_storage_get_tracing+0x2e/0x1b0 bpf_prog_5ea3e95db6da0438_tcp_retransmit_synack+0x1d20/0x1dda bpf_trace_run2+0x4c/0
Засегнати продукти
- Linux Linux: 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af преди 106e457953315e476b3642ef24be25ed862aaba3; 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af преди c964bf65f80a14288d767023a1b300b30f5b9cd0; 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af преди 8459d61fbf24967839a70235165673148c7c7f17; 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af преди 5071beb59ee416e8ab456ac8647a4dabcda823b1; 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af преди 997ae8da14f1639ce6fb66a063dab54031cd61b3; 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af преди 51e34db64f4e43c7b055ccf881b7f3e0c31bb26d; 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af преди e8c526f2bdf1845bedaf6a478816a3d06fa78b8f; d3a1196bfc462943694623412d8e03aaf172bdc1; 4.1.11 преди 4.2
- Linux Linux: 4.2; преди 4.2; 5.4.293 до 5.4.*; 5.10.237 до 5.10.*; 5.15.170 до 5.15.*; 6.1.115 до 6.1.*; 6.6.59 до 6.6.*; 6.11.6 до 6.11.*; 6.12 до *
Вид слабост
История
- 7 ноември 2024 Публикувано
Други уязвимости в Linux Linux
Първоизточници
- https://www.cve.org/CVERecord?id=CVE-2024-50154
- https://nvd.nist.gov/vuln/detail/CVE-2024-50154
- https://git.kernel.org/stable/c/106e457953315e476b3642ef24be25ed862aaba3
- https://git.kernel.org/stable/c/c964bf65f80a14288d767023a1b300b30f5b9cd0
- https://git.kernel.org/stable/c/8459d61fbf24967839a70235165673148c7c7f17
- https://git.kernel.org/stable/c/5071beb59ee416e8ab456ac8647a4dabcda823b1
- https://git.kernel.org/stable/c/997ae8da14f1639ce6fb66a063dab54031cd61b3
- https://git.kernel.org/stable/c/51e34db64f4e43c7b055ccf881b7f3e0c31bb26d
- https://git.kernel.org/stable/c/e8c526f2bdf1845bedaf6a478816a3d06fa78b8f
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html