CVE-2022-50045 json
powerpc/pci: Fix get_phb_number() locking
published 2025-06-18 16 mo ago modified 2026-11-05 3 d ago also EUVD-2022-55316
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.138, 5.15.63, 5.19, 5.19.4
- linux Debian 14, Debian 13, Debian 12 6.0.2-1
debian advisories DEBIAN-CVE-2022-50045
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.170.2
- kernel-syms SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +3 more 5.14.21-150400.24.170.1
- kernel-source SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +3 more 5.14.21-150400.24.170.1
- kernel-default SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +6 more 5.14.21-150400.24.170.2
- kernel-zfcpdump SLES 15 SP4-LTSS, Manager Server 4.3 5.14.21-150400.24.170.2
- kernel-obs-build SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.170.2
- kernel-default-base SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +5 more 5.14.21-150400.24.170.2.150400.24.86.2
- kernel-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.124.1
suse advisories SUSE-SU-2025:02537-1SUSE-SU-2025:02334-1SUSE-SU-2025:02322-1SUSE-SU-2025:02321-1SUSE-SU-2025:02320-1SUSE-SU-2025:02308-1
- git.kernel.org/stable/c/6f75057c21eab12c6ccb7f06f859641a6edfab99 commit
- git.kernel.org/stable/c/5db5ce0f1963c6c8275719a80cb65e9c98d32726 commit
- git.kernel.org/stable/c/ccb0a42d3f40c436295e0fef57ab613ae5b925a4 commit
- git.kernel.org/stable/c/a868f771ee41c97a25a04b8c632a7f06689b307b commit
- git.kernel.org/stable/c/1d9e75c3d8cdf7c96a94cb77450d4ee070279e6a commit
- git.kernel.org/stable/c/90f195c01a2e8d8da6281791617e21109719c981 commit
- git.kernel.org/stable/c/8d48562a2729742f767b0fdd994d6b2a56a49c63 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-50045 updated cvss 2.5
kernel: powerpc/pci: Fix get_phb_number() locking
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available
-
Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-667 Improper Locking
- Technology feeds
References
-
git.kernel.org
/stable/c/6f75057c21eab12c6ccb7f06f859641a6edfab99
patch
-
git.kernel.org
/stable/c/5db5ce0f1963c6c8275719a80cb65e9c98d32726
patch
-
git.kernel.org
/stable/c/ccb0a42d3f40c436295e0fef57ab613ae5b925a4
patch
-
git.kernel.org
/stable/c/a868f771ee41c97a25a04b8c632a7f06689b307b
patch
-
git.kernel.org
/stable/c/1d9e75c3d8cdf7c96a94cb77450d4ee070279e6a
patch
-
git.kernel.org
/stable/c/90f195c01a2e8d8da6281791617e21109719c981
patch
-
git.kernel.org
/stable/c/8d48562a2729742f767b0fdd994d6b2a56a49c63
patch
Sources
- CVE List CVE-2022-50045
- NVD CVE-2022-50045
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.