This vulnerability in the Linux kernel involves a deadlock caused by an unsafe lock order between SOFTIRQ-safe and SOFTIRQ-unsafe contexts during fasync signaling for process groups. Specifically, send_sigio() and send_sigurg() functions use read_lock(&tasklist_lock) while operating in softirq context, conflicting with write_lock(&tasklist_lock) attempts in process context (e.g., fork() or exit()). This leads to a deadlock when a softirq interrupts a process holding a read lock and tries to acquire the same lock again while a writer is waiting. The root cause is the rwlock writer fairness mechanism combined with lock acquisition order. Since PID hashing and task traversal are already RCU-protected, the patch replaces tasklist_lock with rcu_read_lock(), aligning signaling paths and mitigating the deadlock and a potential remote denial of service via TCP URG packets.

The vulnerability can cause a system deadlock leading to denial of service, triggered remotely through TCP URG packets. There is no impact on confidentiality or integrity, but availability is severely affected due to the deadlock condition. No known exploits are reported in the wild.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described fix replaces the tasklist_lock with rcu_read_lock() in the signaling path to prevent deadlocks. Until an official patch is available, monitoring for unusual system hangs related to TCP URG packets may be prudent.