CVE-2022-50045 Vulnerability Analysis & Exploit Details

CVE-2022-50045
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2022-50045 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-50045 Details

Status: Analyzed

Last updated: 🕡 13 Nov 2025, 18:39 UTC
Originally published on: 🕚 18 Jun 2025, 11:15 UTC

Time between publication and last update: 148 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE-2022-50045 Vulnerability Summary

CVE-2022-50045: 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.

Assessing the Risk of CVE-2022-50045

Access Complexity Graph

The exploitability of CVE-2022-50045 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2022-50045

CVE-2022-50045 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2022-50045, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2022-50045, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2022-50045 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2022-50045 poses no threat to data integrity.
  • Availability: High
    CVE-2022-50045 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2022-50045 References

External References

CWE Common Weakness Enumeration

CWE-667

CAPEC Common Attack Pattern Enumeration and Classification

  • Forced Deadlock CAPEC-25 The adversary triggers and exploits a deadlock condition in the target software to cause a denial of service. A deadlock can occur when two or more competing actions are waiting for each other to finish, and thus neither ever does. Deadlock conditions can be difficult to detect.
  • Leveraging Race Conditions CAPEC-26 The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
  • Leveraging Race Conditions via Symbolic Links CAPEC-27 This attack leverages the use of symbolic links (Symlinks) in order to write to sensitive files. An attacker can create a Symlink link to a target file not otherwise accessible to them. When the privileged program tries to create a temporary file with the same name as the Symlink link, it will actually write to the target file pointed to by the attackers' Symlink link. If the attacker can insert malicious content in the temporary file they will be writing to the sensitive file by using the Symlink. The race occurs because the system checks if the temporary file exists, then creates the file. The attacker would typically create the Symlink during the interval between the check and the creation of the temporary file.

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:5.15.61:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.61:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.62:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.62:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.18:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.18:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18.19:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18.19:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.18:rc9:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.18:rc9:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.10.137:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.10.137:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0:rc1:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-50045: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-66026 – REDAXO is a PHP-based CMS. Prior to version 5.20.1, a reflected Cross-Site Scripting (XSS) vulnerability exists in the Mediapool view where the req...
  • CVE-2025-66025 – Caido is a web security auditing toolkit. Prior to version 0.53.0, the Markdown renderer used in Caido’s Findings page improperly handled user-supp...
  • CVE-2025-66022 – FACTION is a PenTesting Report Generation and Collaboration Framework. Prior to version 1.7.1, an extension execution path in Faction’s extension f...
  • CVE-2025-66269 – The RupsMon and USBMate services in UPSilon 2000 run with SYSTEM privileges and contain unquoted service paths. This allows a local attacker to per...
  • CVE-2025-66266 – The RupsMon.exe service executable in UPSilon 2000 has insecure permissions, allowing the 'Everyone' group Full Control. A local attacker can repla...