CVE-2022-50045: powerpc/pci: Fix get_phb_number() locking
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1d9e75c3d8cdf7c96a94cb77450d4ee070279e6a, 5.10.138, 5.15.63.
Low priority for now. Upgrade to Linux Linux 1d9e75c3d8cdf7c96a94cb77450d4ee070279e6a, 5.10.138, 5.15.63 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: powerpc/pci: Fix get_phb_number() locking The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP warning on some systems: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper preempt_count: 1, expected: 0 RCU nest depth: 0, expected: 0 1 lock held by swapper/1: #0: c157efb0 (hose_spinlock){+.+.}-{2:2}, at: pcibios_alloc_controller+0x64/0x220 Preemption disabled at: [<00000000>] 0x0 CPU: 0 PID: 1 Comm: swapper Not tainted 5.19.0-yocto-standard+ #1 Call Trace: [d101dc90] [c073b264] dump_stack_lvl+0x50/0x8c (unreliable) [d101dcb0] [c0093b70] __might_resched+0x258/0x2a8 [d101dcd0] [c0d3e634] __mutex_lock+0x6c/0x6ec [d101dd50] [c0a84174] of_alias_get_id+0x50/0xf4 [d101dd80] [c002ec78] pcibios_alloc_controller+0x1b8/0x220 [d101ddd0] [c140c9dc] pmac_pci_init+0x198/0x784 [d101de50] [c140852c] discover_phbs+0x30/0x4c [d101de60] [c0007fd4] do_one_initcall+0x94/0x344 [d101ded0] [c1403b40] kernel_init_freeable+0x1a8/0x22c [d101df10] [c00086e0] kernel_init+0x34/0x160 [d101df30] [c001b334] ret_from_kernel_thread+0x5c/0x64 This is because pcibios_alloc_controller() holds hose_spinlock but of_alias_get_id() takes of_mutex which can sleep. The hose_spinlock protects the phb_bitmap, and also the hose_list, but it doesn't need to be held while get_phb_number() calls the OF routines, because those are only looking up information in the device tree. So fix it by having get_phb_number() take the hose_spinlock itself, only where required, and then dropping the lock before returning. pcibios_alloc_controller() then needs to take the lock again before the list_add() but that's safe, the order of the list is not important.
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15.61 and later · before 5.15.63
- linux linux kernel5.18.18 and later · before 5.19
- linux linux kernel5.19.2 and later · before 5.19.4
- linux linux kernel5.10.137
- linux linux kernel6.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- e0274da3ac318296fed503422ccda98ce67e99cbaffected
- a79e4395619c926ea7e828b2023c0fbe2776385b and later · before 6f75057c21eab12c6ccb7f06f859641a6edfab99affected · git
- 205826dcac3271ab04fb97d66f1b4f8219723259 and later · before 5db5ce0f1963c6c8275719a80cb65e9c98d32726affected · git
- 3ec50b8a0128359ff4ad4061a75c3322d0ab6ac9 and later · before ccb0a42d3f40c436295e0fef57ab613ae5b925a4affected · git
- 47a8fe1b154aa6d836582365b1c70684af8597e4 and later · before a868f771ee41c97a25a04b8c632a7f06689b307baffected · git
- ef0f4eeaba2463a77ac5a4e42c30717deb3c7b62 and later · before 1d9e75c3d8cdf7c96a94cb77450d4ee070279e6aaffected · git
- f35c7f506fb96a23a1961c7314c5931ec8bc473e and later · before 90f195c01a2e8d8da6281791617e21109719c981affected · git
- 0fe1e96fef0a5c53b4c0d1500d356f3906000f81 and later · before 8d48562a2729742f767b0fdd994d6b2a56a49c63affected · git
- 5.18.18 and later · before 5.19affected · semver
- 5.10.137 and later · before 5.10.138affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.2-1 | 6.0.2-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50043Jun 18, 2025 · net: fix potential refcount leak in ndisc_router_discovery()22Monitor
- ← EarlierCVE-2022-50044Jun 18, 2025 · net: qrtr: start MHI channel after endpoit creation18Monitor
- Later →CVE-2022-50046Jun 18, 2025 · net/sunrpc: fix potential memory leaks in rpc_sysfs_xprt_state_change()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1d9e75c3d8cdf7c96a94cb77450d4ee070279e6a | Vendor (CNA) |
| Linux Linux | 5.10.138 | Vendor (CNA) |
| Linux Linux | 5.15.63 | Vendor (CNA) |
| Linux Linux | 5.19 | Vendor (CNA) |
| Linux Linux | 5.19.4 | Vendor (CNA) |
| Linux Linux | 5db5ce0f1963c6c8275719a80cb65e9c98d32726 | Vendor (CNA) |
| Linux Linux | 6f75057c21eab12c6ccb7f06f859641a6edfab99 | Vendor (CNA) |
| Linux Linux | 8d48562a2729742f767b0fdd994d6b2a56a49c63 | Vendor (CNA) |
| Linux Linux | 90f195c01a2e8d8da6281791617e21109719c981 | Vendor (CNA) |
| Linux Linux | a868f771ee41c97a25a04b8c632a7f06689b307b | Vendor (CNA) |
| Linux Linux | ccb0a42d3f40c436295e0fef57ab613ae5b925a4 | Vendor (CNA) |
| debian:linux | 6.0.2-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/5db5ce0f1963c6c8275719a80cb65e9c98d32726
- git.kernel.org/stable/c/6f75057c21eab12c6ccb7f06f859641a6edfab99
- git.kernel.org/stable/c/8d48562a2729742f767b0fdd994d6b2a56a49c63
- git.kernel.org/stable/c/90f195c01a2e8d8da6281791617e21109719c981
- git.kernel.org/stable/c/a868f771ee41c97a25a04b8c632a7f06689b307b
- git.kernel.org/stable/c/ccb0a42d3f40c436295e0fef57ab613ae5b925a4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.