System hang via panic-time device-tree deadlock
Published Dec 30, 2025 · Updated Dec 30, 2025
A deadlock in the Linux kernel's PowerPC RTAS panic path allows local users to hang affected systems through a kernel panic. The rtas_os_term() function traverses the /rtas device-tree node while panic handling can already hold devtree_lock, causing a recursive lock wait. The flaw is limited to PowerPC systems using RTAS, and the hang occurs only when panic handling runs while devtree_lock is held.
Summary
What happened
A deadlock in the Linux kernel's PowerPC RTAS panic path allows local users to hang affected systems through a kernel panic. The rtas_os_term() function traverses the /rtas device-tree node while panic handling can already hold devtree_lock, causing a recursive lock wait. The flaw is limited to PowerPC systems using RTAS, and the hang occurs only when panic handling runs while devtree_lock is held.
The record
- CVE
- CVE-2022-50870
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <06a07fbb32b3a23eec20a42b1e64474da0a3b33e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <464d10e8d797454e16a173ef1292a446b2adf21c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <698e682c849e356fb47a8be47ca8baa817cf31e0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c2fa91abf22a705cf02f886cd99cff41f4ceda60
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d8939315b7342860df143afe0adda6212cdd3193
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e23822c7381c59d9e42e65771b6e17c71ed30ea7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ed2213bfb192ab51f09f12e9b49b5d482c6493f3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f2167f10fcca68ab9ae3f8d94d2c704c5541ac69
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.
Weakness, pattern, technique
No sourced classifications are available.
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