Количество 16
Количество 16
CVE-2022-50091
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.
CVE-2022-50091
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.
CVE-2022-50091
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.
CVE-2022-50091
In the Linux kernel, the following vulnerability has been resolved: l ...
GHSA-22j6-v8cr-pvvx
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.
BDU:2026-02804
Уязвимость функции csdlock_debug() модуля kernel/smp.c ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
SUSE-SU-2025:02334-1
Security update for the Linux Kernel
SUSE-SU-2025:02308-1
Security update for the Linux Kernel
ALT-PU-2022-2474
ALT-PU-2022-2474: package `kernel-image-un-def` update to version 5.15.61-alt1
ALT-PU-2022-2454
ALT-PU-2022-2454: package `kernel-image-std-def` update to version 5.15.61-alt1
ALT-PU-2022-2453
ALT-PU-2022-2453: package `kernel-image-un-def` update to version 5.18.18-alt1
ALT-PU-2022-2497
ALT-PU-2022-2497: package `kernel-image-mp` update to version 5.19.4-alt1
ALT-PU-2022-2692
ALT-PU-2022-2692: package `kernel-image-rpi-def` update to version 5.15.70-alt1
ALT-PU-2022-2682
ALT-PU-2022-2682: package `kernel-image-rpi-def` update to version 5.15.70-alt1
ALT-PU-2022-2919
ALT-PU-2022-2919: package `kernel-image-rpi-un` update to version 6.0.2-alt1
ALT-PU-2022-2915
ALT-PU-2022-2915: package `kernel-image-rpi-un` update to version 6.0.2-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2022-50091 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. | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2022-50091 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. | CVSS3: 7 | 0% Низкий | больше 1 года назад | |
CVE-2022-50091 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. | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2022-50091 In the Linux kernel, the following vulnerability has been resolved: l ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
GHSA-22j6-v8cr-pvvx 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. | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
BDU:2026-02804 Уязвимость функции csdlock_debug() модуля kernel/smp.c ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 7 | 0% Низкий | больше 4 лет назад | |
SUSE-SU-2025:02334-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:02308-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2022-2474 ALT-PU-2022-2474: package `kernel-image-un-def` update to version 5.15.61-alt1 | CVSS3: 10 | около 4 лет назад | ||
ALT-PU-2022-2454 ALT-PU-2022-2454: package `kernel-image-std-def` update to version 5.15.61-alt1 | CVSS3: 10 | около 4 лет назад | ||
ALT-PU-2022-2453 ALT-PU-2022-2453: package `kernel-image-un-def` update to version 5.18.18-alt1 | CVSS3: 10 | около 4 лет назад | ||
ALT-PU-2022-2497 ALT-PU-2022-2497: package `kernel-image-mp` update to version 5.19.4-alt1 | CVSS3: 10 | около 4 лет назад | ||
ALT-PU-2022-2692 ALT-PU-2022-2692: package `kernel-image-rpi-def` update to version 5.15.70-alt1 | CVSS3: 10 | около 4 лет назад | ||
ALT-PU-2022-2682 ALT-PU-2022-2682: package `kernel-image-rpi-def` update to version 5.15.70-alt1 | CVSS3: 10 | около 4 лет назад | ||
ALT-PU-2022-2919 ALT-PU-2022-2919: package `kernel-image-rpi-un` update to version 6.0.2-alt1 | CVSS3: 10 | почти 4 года назад | ||
ALT-PU-2022-2915 ALT-PU-2022-2915: package `kernel-image-rpi-un` update to version 6.0.2-alt1 | CVSS3: 10 | почти 4 года назад |
Уязвимостей на страницу