# powerpc/pci: Fix get_phb_number() locking

CVE record · `CVE-2022-50045`

- **Identifiers:** `CVE-2022-50045`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 18 Jun 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 18 Jun 2025, 11:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `a79e4395619c926ea7e828b2023c0fbe2776385b to before 6f75057c21eab12c6ccb7f06f859641a6edfab99` (git)
  - affected: `205826dcac3271ab04fb97d66f1b4f8219723259 to before 5db5ce0f1963c6c8275719a80cb65e9c98d32726` (git)
  - affected: `3ec50b8a0128359ff4ad4061a75c3322d0ab6ac9 to before ccb0a42d3f40c436295e0fef57ab613ae5b925a4` (git)
  - affected: `47a8fe1b154aa6d836582365b1c70684af8597e4 to before a868f771ee41c97a25a04b8c632a7f06689b307b` (git)
  - affected: `ef0f4eeaba2463a77ac5a4e42c30717deb3c7b62 to before 1d9e75c3d8cdf7c96a94cb77450d4ee070279e6a` (git)
  - affected: `f35c7f506fb96a23a1961c7314c5931ec8bc473e to before 90f195c01a2e8d8da6281791617e21109719c981` (git)
  - affected: `0fe1e96fef0a5c53b4c0d1500d356f3906000f81 to before 8d48562a2729742f767b0fdd994d6b2a56a49c63` (git)
  - affected: `e0274da3ac318296fed503422ccda98ce67e99cb` (git)
  - affected: `5.18.18 to before 5.19` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.10.137 to before 5.10.138` (semver)
  - affected: `5.15.61 to before 5.15.63` (semver)
  - affected: `5.19.2 to before 5.19.4` (semver)
  - Other versions: unaffected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> CVE-2022-50045 affects the Linux kernel's powerpc PCI code, in the get_phb_number() function. A change to that function caused a sleeping-while-atomic warning (a DEBUG_ATOMIC_SLEEP bug) on some systems, because a lock was held while code that can sleep was called. The source gives few details about the impact beyond this kernel warning. The source lists fixed versions as 5.10.138, 5.15.63 and 5.19.4 and later, and the patched upstream commits. Users of affected stable branches should upgrade to a fixed kernel version.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 4th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 18 Jun 2025, 11:01 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50045)
- 18 Jun 2025, 11:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50045)

## Sources

- [CVE List: CVE-2022-50045](https://www.cve.org/CVERecord?id=CVE-2022-50045)
- [NVD: CVE-2022-50045](https://nvd.nist.gov/vuln/detail/CVE-2022-50045)

### References from the CNA

- <https://git.kernel.org/stable/c/6f75057c21eab12c6ccb7f06f859641a6edfab99>
- <https://git.kernel.org/stable/c/5db5ce0f1963c6c8275719a80cb65e9c98d32726>
- <https://git.kernel.org/stable/c/ccb0a42d3f40c436295e0fef57ab613ae5b925a4>
- <https://git.kernel.org/stable/c/a868f771ee41c97a25a04b8c632a7f06689b307b>
- <https://git.kernel.org/stable/c/1d9e75c3d8cdf7c96a94cb77450d4ee070279e6a>
- <https://git.kernel.org/stable/c/90f195c01a2e8d8da6281791617e21109719c981>
- <https://git.kernel.org/stable/c/8d48562a2729742f767b0fdd994d6b2a56a49c63>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-50045>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-50045/>. Everything for agents: <https://agentprime.io/llms.txt>.
