CVE-2022-49303
Last modified
CVE-2022-49303 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: drivers: staging: rtl8192eu: Fix deadlock in rtw_joinbss_event_prehandle There is a deadlock in rtw_joinbss_event_prehandle(), which is shown below: (Thread 1) | (Thread 2) | _set_timer() rtw_joinbss_event_prehandle()| mod_timer() spin_lock_bh() //(1) | (wait a time) ... | rtw_join_timeout_handler() | _rtw_join_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_joinbss_event_prehandle() 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: drivers: staging: rtl8192eu: Fix deadlock in rtw_joinbss_event_prehandle There is a deadlock in rtw_joinbss_event_prehandle(), which is shown below: (Thread 1) | (Thread 2) | _set_timer() rtw_joinbss_event_prehandle()| mod_timer() spin_lock_bh() //(1) | (wait a time) ... | rtw_join_timeout_handler() | _rtw_join_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_joinbss_event_prehandle() 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() to spin_lock_irq() in _rtw_join_timeout_handler() in order to prevent deadlock.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 5.18.4 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-49303?
How severe is CVE-2022-49303?
How do I fix CVE-2022-49303?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-49298In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49299Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2022-4930A vulnerability classified as problematic was found in nuxsm…5.4
- CVE-2022-49300In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2022-49301In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49302In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49304In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49305In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49306In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49307In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49308In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49309In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-49303?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
