System hang via recursive device lock acquisition
Published Jun 18, 2025 · Updated May 11, 2026
Improper locking in the Linux kernel driver core starting in 5.1 allows local users to hang the system during asynchronous driver attachment. The __driver_attach path holds the device lock while scheduling __driver_attach_async_helper, which reacquires that lock when scheduling falls back to synchronous execution. Reaching the deadlock requires an asynchronous probe and allocation failure or saturation of the async-work limit; the resulting uninterruptible wait blocks driver attachment and can stall system startup.
Summary
What happened
Improper locking in the Linux kernel driver core starting in 5.1 allows local users to hang the system during asynchronous driver attachment. The __driver_attach path holds the device lock while scheduling __driver_attach_async_helper, which reacquires that lock when scheduling falls back to synchronous execution. Reaching the deadlock requires an asynchronous probe and allocation failure or saturation of the async-work limit; the resulting uninterruptible wait blocks driver attachment and can stall system startup.
The record
- CVE
- CVE-2022-50149
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.1
- Affected versionversion=ef0ff68351be4fd83bec2d797f0efdc0174a55a4 <37f908038402c9b8325763f306a1c65d88757e15
- Affected versionversion=ef0ff68351be4fd83bec2d797f0efdc0174a55a4 <70fe758352cafdee72a7b13bf9db065f9613ced8
- Affected versionversion=ef0ff68351be4fd83bec2d797f0efdc0174a55a4 <733ab0c19bf17f6ad7c2b580ede006e369d5ab1b
- Affected versionversion=ef0ff68351be4fd83bec2d797f0efdc0174a55a4 <779b634714c51d05baaeff4868ce2fd9fc7399bf
- Affected versionversion=ef0ff68351be4fd83bec2d797f0efdc0174a55a4 <8191b6cd9ada09b675f17446d5872eb1f77685cb
- Affected versionversion=ef0ff68351be4fd83bec2d797f0efdc0174a55a4 <a93f33aeef4e6a94ae9c9d3f5b2f9085ad0572ec
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo