drivers: staging: rtl8723bs: Fix locking in _rtw_join_timeout_handler()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 209850f17717a3b5cc558578bef5631ac7045539, Kernel 2a50e44a66d268ee5db3d177f1fdc1503dbce6e7, Kernel 4ab1bace1dd3875371b481ef4301c4671bddea22 and 8 more.
In the Linux kernel, the following vulnerability has been resolved: drivers: staging: rtl8723bs: Fix locking in _rtw_join_timeout_handler() Commit 041879b12ddb ("drivers: staging: rtl8192bs: Fix deadlock in rtw_joinbss_event_prehandle()") besides fixing the deadlock also modified _rtw_join_timeout_handler() to use spin_[un]lock_irq() instead of spin_[un]lock_bh(). _rtw_join_timeout_handler() calls rtw_do_join() which takes pmlmepriv->scanned_queue.lock using spin_[un]lock_bh(). This spin_unlock_bh() call re-enables softirqs which triggers an oops in kernel/softirq.c: __local_bh_enable_ip() when it calls lockdep_assert_irqs_enabled(): [ 244.506087] WARNING: CPU: 2 PID: 0 at kernel/softirq.c:376 __local_bh_enable_ip+0xa6/0x100 ... [ 244.509022] Call Trace: [ 244.509048] <IRQ> [ 244.509100] _rtw_join_timeout_handler+0x134/0x170 [r8723bs] [ 244.509468] ? __pfx__rtw_join_timeout_handler+0x10/0x10 [r8723bs] [ 244.509772] ? __pfx__rtw_join_timeout_handler+0x10/0x10 [r8723bs] [ 244.510076] call_timer_fn+0x95/0x2a0 [ 244.510200] __run_timers.part.0+0x1da/0x2d0 This oops is causd by the switch to spin_[un]lock_irq() which disables the IRQs for the entire duration of _rtw_join_timeout_handler(). Disabling the IRQs is not necessary since all code taking this lock runs from either user contexts or from softirqs, switch back to spin_[un]lock_bh() to fix this.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=ae60744d5fad840b9d056d35b4b652d95e755846 <209850f17717a3b5cc558578bef5631ac7045539, >=041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc <2a50e44a66d268ee5db3d177f1fdc1503dbce6e7, >=041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc <4ab1bace1dd3875371b481ef4301c4671bddea22, >=041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc <dc327e87c6d9bfd9ee08e76396b3c0ba848ec554, >=5.15.47 <5.15.111, >=5.17.15 <5.18, >=5.18.4 <5.19, =1f6c99b94ca3caad346876b3e22e3ca3d25bc8ee, =5.19, =eca9748d9267a38d532464e3305a38629e9c35a9, >=041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc <215792eda008f6a1e7ed9d77fa20d582d22bb114 | 209850f17717a3b5cc558578bef5631ac7045539, 2a50e44a66d268ee5db3d177f1fdc1503dbce6e7, 4ab1bace1dd3875371b481ef4301c4671bddea22, dc327e87c6d9bfd9ee08e76396b3c0ba848ec554, 5.15.111, 5.18, 5.19, 215792eda008f6a1e7ed9d77fa20d582d22bb114 |
| linux-kernel: Kernel | >=5.17.15 <5.18, >=5.18.4 <5.19, >=5.19.0 <6.1.28, >=6.2.0 <6.2.15, >=6.3.0 <6.3.2, >=5.15.47 <5.15.111 | 5.18, 5.19, 6.1.28, 6.2.15, 6.3.2, 5.15.111 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket