نسخههای متأثر
- نسخههای متأثر
- نامشخص
- نسخهٔ اصلاحشده
- اعلام نشده
بهرهبرداری
شرح آسیبپذیری
In the Linux kernel, the following vulnerability has been resolved: net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks() syzbot is reporting lockdep warning at rds_tcp_reset_callbacks() [1], for commit ac3615e7f3cffe2a ("RDS: TCP: Reduce code duplication in rds_tcp_reset_callbacks()") added cancel_delayed_work_sync() into a section protected by lock_sock() without realizing that rds_send_xmit() might call lock_sock(). We don't need to protect cancel_delayed_work_sync() using lock_sock(), for even if rds_{send,recv}_worker() re-queued this work while _flush_work() from cancel_delayed_work_sync() was waiting for this work to complete, retried rds{send,recv}_worker() is no-op due to the absence of RDS_CONN_UP bit.
A potential deadlock vulnerability was found in the RDS (Reliable Datagram Sockets) TCP transport in the Linux kernel. In rds_tcp_reset_callbacks(), cancel_delayed_work_sync() is called while holding the socket lock (lock_sock()). However, the worker functions rds_send_xmit() and rds_recv_worker() may also try to acquire lock_sock(), creating a deadlock scenario. This can cause the system to hang.

