CVE-2022-49309
What it is
In the Linux kernel, the following vulnerability has been resolved: drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback() There is a deadlock in rtw_surveydone_event_callback(), which is shown below: (Thread 1) | (Thread 2) | _set_timer() rtw_surveydone_event_callback()| mod_timer() spin_lock_bh() //(1) | (wait a time) ... | rtw_scan_timeout_handler() del_timer_sync() | spin_lock_bh() //(2) (wait timer to stop) | ... We hold pmlmepriv->lock in position (1) of thread 1 and use del_timer_sync() to wait timer to stop, but timer handler also need pmlmepriv->lock in position (2) of thread 2. As a result, rtw_surveydone_event_callback() will block forever. This patch extracts del_timer_sync() from the protection of spin_lock_bh(), which could let timer handler to obtain the needed lock. What`s more, we change spin_lock_bh() in rtw_scan_timeout_handler() to spin_lock_irq(). Otherwise, spin_lock_bh() will also cause deadlock() in timer handler.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-667
- Record status
- Modified
Affected
- Linux Kernel < 5.15.47
- Linux Kernel < 5.17.15
- Linux Kernel < 5.18.4
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-49309.md and follow it. Check whether this project is affected by CVE-2022-49309. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/2c41f5c341853f84b7bc2f32605d4e2782e8c279
- https://git.kernel.org/stable/c/cc7ad0d77b51c872d629bcd98aea463a3c4109e7
- https://git.kernel.org/stable/c/ce129d3efd181da5fd56f4360cc8827122afa67e
- https://git.kernel.org/stable/c/f89f6c3ebf69623b8ea48200bd690e9e210335a1
References
- https://git.kernel.org/stable/c/2c41f5c341853f84b7bc2f32605d4e2782e8c279
- https://git.kernel.org/stable/c/c84e5c819600ee0628f61b33d145258ae0f3d7a7
- https://git.kernel.org/stable/c/cc7ad0d77b51c872d629bcd98aea463a3c4109e7
- https://git.kernel.org/stable/c/ce129d3efd181da5fd56f4360cc8827122afa67e
- https://git.kernel.org/stable/c/f89f6c3ebf69623b8ea48200bd690e9e210335a1
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html