CVE-2022-49313
Last modified
CVE-2022-49313 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: drivers: usb: host: Fix deadlock in oxu_bus_suspend() There is a deadlock in oxu_bus_suspend(), which is shown below: (Thread 1) | (Thread 2) | timer_action() oxu_bus_suspend() | mod_timer() spin_lock_irq() //(1) | (wait a time) ... | oxu_watchdog() del_timer_sync() | spin_lock_irq() //(2) (wait timer to stop) | ... We hold oxu->lock in position (1) of thread 1, and use del_timer_sync() to wait timer to stop, but timer handler also need oxu->lock in position (2) of thread 2. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: drivers: usb: host: Fix deadlock in oxu_bus_suspend() There is a deadlock in oxu_bus_suspend(), which is shown below: (Thread 1) | (Thread 2) | timer_action() oxu_bus_suspend() | mod_timer() spin_lock_irq() //(1) | (wait a time) ... | oxu_watchdog() del_timer_sync() | spin_lock_irq() //(2) (wait timer to stop) | ... We hold oxu->lock in position (1) of thread 1, and use del_timer_sync() to wait timer to stop, but timer handler also need oxu->lock in position (2) of thread 2. As a result, oxu_bus_suspend() will block forever. This patch extracts del_timer_sync() from the protection of spin_lock_irq(), which could let timer handler to obtain the needed lock.
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 | < 4.9.318 |
| Linux | Linux Kernel | >= 4.10, < 4.14.283 |
| Linux | Linux Kernel | >= 4.15, < 4.19.247 |
| Linux | Linux Kernel | >= 4.20, < 5.4.198 |
| Linux | Linux Kernel | >= 5.5, < 5.10.122 |
| Linux | Linux Kernel | >= 5.11, < 5.15.47 |
| Linux | Linux Kernel | >= 5.16, < 5.17.15 |
| Linux | Linux Kernel | >= 5.18, < 5.18.4 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-49313?
How severe is CVE-2022-49313?
How do I fix CVE-2022-49313?
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-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
- CVE-2022-4931The BackupWordPress plugin for WordPress is vulnerable to in…4.3
- CVE-2022-49310In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49311In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49312In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49314In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49315In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49316In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49317In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49318In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49319In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-49313?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
