CVE-2022-50091
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves the Linux kernel's handling of the csdlock_debug kernel-boot parameter. When set, csdlock_debug() enables a feature called csd_lock_wait via static_branch_enable(). However, on certain kernel configurations (specifically arm64 with CONFIG_SPARSEMEM=y and CONFIG_SPARSEMEM_VMEMMAP=n), this causes a NULL pointer dereference leading to a kernel panic because a required memory section is not yet initialized. A similar issue occurs on powerpc architectures due to early invocation of early_param() functions before jump_label_init(), causing failures in static_key_enable(). The fix changes csdlock_debug from being parsed too early (early_param) to a later stage (__setup) to prevent these failures.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to panic (crash) on affected systems when the csdlock_debug parameter is set under specific kernel configurations. This can lead to system instability, unexpected reboots, or denial of service, impacting availability and reliability of the system.