Menu

Star on GitHub · 3.2k

CVE-2022-50091

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: locking/csd_lock: Change csdlock_debug from early_param to __setup The csdlock_debug kernel-boot parameter is parsed by the ear…

Published Jun 18, 2025CWE-476EPSS 0.25%

Overview

CVE-2022-50091 is a medium-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

locking/csd_lock: Change csdlock_debug from early_param to __setup

The csdlock_debug kernel-boot parameter is parsed by the

early_param() function csdlock_debug(). If set, csdlock_debug()

invokes static_branch_enable() to enable csd_lock_wait feature, which

triggers a panic on arm64 for kernels built with CONFIG_SPARSEMEM=y and

CONFIG_SPARSEMEM_VMEMMAP=n.

With CONFIG_SPARSEMEM_VMEMMAP=n, __nr_to_section is called in

static_key_enable() and returns NULL, resulting in a NULL dereference

because mem_section is initialized only later in sparse_init().

This is also a problem for powerpc because early_param() functions

are invoked earlier than jump_label_init(), also resulting in

static_key_enable() failures. These failures cause the warning "static

key 'xxx' used before call to jump_label_init()".

Thus, early_param is too early for csd_lock_wait to run

static_branch_enable(), so changes it to __setup to fix these.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-50091?

CVE-2022-50091 is a medium-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2022-50091?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-50091?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50091?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50091 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2022

View all