https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 09:18:59 +0000 https://vulnerability.circl.lu/vuln/cve-2023-52638 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock</p> <p>The following 3 locks would race against each other, causing the deadlock situation in the Syzbot bug report:</p> <p>- j1939_socks_lock - active_session_list_lock - sk_session_queue_lock</p> <p>A reasonable fix is to change j1939_socks_lock to an rwlock, since in the rare situations where a write lock is required for the linked list that j1939_socks_lock is protecting, the code does not attempt to acquire any more locks. This would break the circular lock dependency, where, for example, the current thread already locks j1939_socks_lock and attempts to acquire sk_session_queue_lock, and at the same time, another thread attempts to acquire j1939_socks_lock while holding sk_session_queue_lock.</p> <p>NOTE: This patch along does not fix the unregister_netdevice bug reported by Syzbot; instead, it solves a deadlock situation to prepare for one or more further patches to actually fix the Syzbot bug, which appears to be a reference counting problem within the j1939 codebase.</p> <p>[mkl: remove unrelated newline change]</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock</p> <p>The following 3 locks would race against each other, causing the deadlock situation in the Syzbot bug report:</p> <p>- j1939_socks_lock - active_session_list_lock - sk_session_queue_lock</p> <p>A reasonable fix is to change j1939_socks_lock to an rwlock, since in the rare situations where a write lock is required for the linked list that j1939_socks_lock is protecting, the code does not attempt to acquire any more locks. This would break the circular lock dependency, where, for example, the current thread already locks j1939_socks_lock and attempts to acquire sk_session_queue_lock, and at the same time, another thread attempts to acquire j1939_socks_lock while holding sk_session_queue_lock.</p> <p>NOTE: This patch along does not fix the unregister_netdevice bug reported by Syzbot; instead, it solves a deadlock situation to prepare for one or more further patches to actually fix the Syzbot bug, which appears to be a reference counting problem within the j1939 codebase.</p> <p>[mkl: remove unrelated newline change]</p> https://vulnerability.circl.lu/vuln/cve-2023-52638