CVE-2023-53281
drivers: staging: rtl8723bs: Fix locking in _rtw_join_timeout_handler()
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (7 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Weakness
Affected products
- affected ae60744d5fad840b9d056d35b4b652d95e755846 – < 209850f17717a3b5cc558578bef5631ac7045539
- affected 041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc – < 2a50e44a66d268ee5db3d177f1fdc1503dbce6e7
- affected 041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc – < dc327e87c6d9bfd9ee08e76396b3c0ba848ec554
- affected 041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc – < 4ab1bace1dd3875371b481ef4301c4671bddea22
- affected 041879b12ddb0c6c83ed9c0bdd10dc82a056f2fc – < 215792eda008f6a1e7ed9d77fa20d582d22bb114
- affected 1f6c99b94ca3caad346876b3e22e3ca3d25bc8ee
- affected eca9748d9267a38d532464e3305a38629e9c35a9
- affected 5.15.47 – < 5.15.111
- affected 5.17.15 – < 5.18
- affected 5.18.4 – < 5.19
- affected 5.19
- unaffected < 5.19
- unaffected 5.15.111 – ≤ 5.15.*
- unaffected 6.1.28 – ≤ 6.1.*
- unaffected 6.2.15 – ≤ 6.2.*
- unaffected 6.3.2 – ≤ 6.3.*
- unaffected 6.4 – ≤ *
References (5)
- https://git.kernel.org/stable/c/209850f17717a3b5cc558578bef5631ac7045539 (opens in a new tab)
- https://git.kernel.org/stable/c/2a50e44a66d268ee5db3d177f1fdc1503dbce6e7 (opens in a new tab)
- https://git.kernel.org/stable/c/dc327e87c6d9bfd9ee08e76396b3c0ba848ec554 (opens in a new tab)
- https://git.kernel.org/stable/c/4ab1bace1dd3875371b481ef4301c4671bddea22 (opens in a new tab)
- https://git.kernel.org/stable/c/215792eda008f6a1e7ed9d77fa20d582d22bb114 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2023-53281)Record last updated .