Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50091

locking/csd_lock: Change csdlock_debug from early_param to __setup

Medium5.5EPSS 0.25%
Published
Updated
Reserved
Assigned by
Linux

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 17 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50091, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.25% · top 83% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

Affected products

  • Linux · Linux

    • affected 8d0968cc6b8ffd8496c2ebffdfdc801f949a85e5 – < d2cbdbe22b5f190055d2d0ae92e7454479343a30
    • affected 8d0968cc6b8ffd8496c2ebffdfdc801f949a85e5 – < 05de9e2e33b1625c71aee69e353fe906dd2be88a
    • affected 8d0968cc6b8ffd8496c2ebffdfdc801f949a85e5 – < b480d1e9a8c11ecc1c99dc01814b28e3103bd0a0
    • affected 8d0968cc6b8ffd8496c2ebffdfdc801f949a85e5 – < 9c9b26b0df270d4f9246e483a44686fca951a29c
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.61 – ≤ 5.15.*
    • unaffected 5.18.18 – ≤ 5.18.*
    • unaffected 5.19.2 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References (4)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50091 badge
[![CVE-2022-50091](https://trackcve.app/badge/CVE-2022-50091.svg)](https://trackcve.app/cve/CVE-2022-50091)

Record last updated .