Количество 21
Количество 21
CVE-2026-64373
In the Linux kernel, the following vulnerability has been resolved: cpufreq: Fix hotplug-suspend race during reboot During system reboot, cpufreq_suspend() is called via the kernel_restart() -> device_shutdown() path. Unlike the normal system suspend path, the reboot path does not call freeze_processes(), so userspace processes and kernel threads remain active. This allows CPU hotplug operations to run concurrently with cpufreq_suspend(). The original code has no synchronization with CPU hotplug, leading to a race condition where governor_data can be freed by the hotplug path while cpufreq_suspend() is still accessing it, resulting in a null pointer dereference: Unable to handle kernel NULL pointer dereference Call Trace: do_kernel_fault+0x28/0x3c cpufreq_suspend+0xdc/0x160 device_shutdown+0x18/0x200 kernel_restart+0x40/0x80 arm64_sys_reboot+0x1b0/0x200 Fix this by adding cpus_read_lock()/cpus_read_unlock() to cpufreq_suspend() to block CPU hotplug operations while suspend is in pro...
CVE-2026-64373
In the Linux kernel, the following vulnerability has been resolved: cpufreq: Fix hotplug-suspend race during reboot During system reboot, cpufreq_suspend() is called via the kernel_restart() -> device_shutdown() path. Unlike the normal system suspend path, the reboot path does not call freeze_processes(), so userspace processes and kernel threads remain active. This allows CPU hotplug operations to run concurrently with cpufreq_suspend(). The original code has no synchronization with CPU hotplug, leading to a race condition where governor_data can be freed by the hotplug path while cpufreq_suspend() is still accessing it, resulting in a null pointer dereference: Unable to handle kernel NULL pointer dereference Call Trace: do_kernel_fault+0x28/0x3c cpufreq_suspend+0xdc/0x160 device_shutdown+0x18/0x200 kernel_restart+0x40/0x80 arm64_sys_reboot+0x1b0/0x200 Fix this by adding cpus_read_lock()/cpus_read_unlock() to cpufreq_suspend() to block CPU hotplug operations while suspend is in pro...
CVE-2026-64373
In the Linux kernel, the following vulnerability has been resolved: cpufreq: Fix hotplug-suspend race during reboot During system reboot, cpufreq_suspend() is called via the kernel_restart() -> device_shutdown() path. Unlike the normal system suspend path, the reboot path does not call freeze_processes(), so userspace processes and kernel threads remain active. This allows CPU hotplug operations to run concurrently with cpufreq_suspend(). The original code has no synchronization with CPU hotplug, leading to a race condition where governor_data can be freed by the hotplug path while cpufreq_suspend() is still accessing it, resulting in a null pointer dereference: Unable to handle kernel NULL pointer dereference Call Trace: do_kernel_fault+0x28/0x3c cpufreq_suspend+0xdc/0x160 device_shutdown+0x18/0x200 kernel_restart+0x40/0x80 arm64_sys_reboot+0x1b0/0x200 Fix this by adding cpus_read_lock()/cpus_read_unlock() to cpufreq_suspend() to block CPU hotplug operations wh
CVE-2026-64373
cpufreq: Fix hotplug-suspend race during reboot
CVE-2026-64373
In the Linux kernel, the following vulnerability has been resolved: c ...
ROS-20261008-80-0280
Уязвимость kernel-lt
ROS-20261008-73-0281
Уязвимость kernel-lt
GHSA-r493-vrrx-v3x2
In the Linux kernel, the following vulnerability has been resolved: cpufreq: Fix hotplug-suspend race during reboot During system reboot, cpufreq_suspend() is called via the kernel_restart() -> device_shutdown() path. Unlike the normal system suspend path, the reboot path does not call freeze_processes(), so userspace processes and kernel threads remain active. This allows CPU hotplug operations to run concurrently with cpufreq_suspend(). The original code has no synchronization with CPU hotplug, leading to a race condition where governor_data can be freed by the hotplug path while cpufreq_suspend() is still accessing it, resulting in a null pointer dereference: Unable to handle kernel NULL pointer dereference Call Trace: do_kernel_fault+0x28/0x3c cpufreq_suspend+0xdc/0x160 device_shutdown+0x18/0x200 kernel_restart+0x40/0x80 arm64_sys_reboot+0x1b0/0x200 Fix this by adding cpus_read_lock()/cpus_read_unlock() to cpufreq_suspend() to block CPU hotplug operations...
ALT-PU-2019-3291
ALT-PU-2019-3291: package `kernel-image-un-def` update to version 5.4.0-alt1
ALT-PU-2026-11928
ALT-PU-2026-11928: package `kernel-image-std-def` update to version 5.10.262-alt1
ALT-PU-2026-11926
ALT-PU-2026-11926: package `kernel-image-un-def` update to version 6.1.180-alt1
ALT-PU-2026-12325
ALT-PU-2026-12325: package `kernel-image-for-vm` update to version 6.18.40-alt1
SUSE-SU-2026:4687-1
Security update for the Linux Kernel
ALT-PU-2026-11249
ALT-PU-2026-11249: package `kernel-image-6.12` update to version 6.12.96-alt1
ALT-PU-2026-11606
ALT-PU-2026-11606: package `kernel-image-6.18` update to version 6.18.40-alt1
SUSE-SU-2026:4706-1
Security update for the Linux Kernel
SUSE-SU-2026:4640-1
Security update for the Linux Kernel
ELSA-2026-500249
ELSA-2026-500249: Unbreakable Enterprise kernel security update (IMPORTANT)
openSUSE-SU-2026:21910-1
Security update for the Linux Kernel
ELSA-2026-500248
ELSA-2026-500248: Unbreakable Enterprise kernel security update (IMPORTANT)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-64373 In the Linux kernel, the following vulnerability has been resolved: cpufreq: Fix hotplug-suspend race during reboot During system reboot, cpufreq_suspend() is called via the kernel_restart() -> device_shutdown() path. Unlike the normal system suspend path, the reboot path does not call freeze_processes(), so userspace processes and kernel threads remain active. This allows CPU hotplug operations to run concurrently with cpufreq_suspend(). The original code has no synchronization with CPU hotplug, leading to a race condition where governor_data can be freed by the hotplug path while cpufreq_suspend() is still accessing it, resulting in a null pointer dereference: Unable to handle kernel NULL pointer dereference Call Trace: do_kernel_fault+0x28/0x3c cpufreq_suspend+0xdc/0x160 device_shutdown+0x18/0x200 kernel_restart+0x40/0x80 arm64_sys_reboot+0x1b0/0x200 Fix this by adding cpus_read_lock()/cpus_read_unlock() to cpufreq_suspend() to block CPU hotplug operations while suspend is in pro... | CVSS3: 4.7 | 0% Низкий | 3 месяца назад | |
CVE-2026-64373 In the Linux kernel, the following vulnerability has been resolved: cpufreq: Fix hotplug-suspend race during reboot During system reboot, cpufreq_suspend() is called via the kernel_restart() -> device_shutdown() path. Unlike the normal system suspend path, the reboot path does not call freeze_processes(), so userspace processes and kernel threads remain active. This allows CPU hotplug operations to run concurrently with cpufreq_suspend(). The original code has no synchronization with CPU hotplug, leading to a race condition where governor_data can be freed by the hotplug path while cpufreq_suspend() is still accessing it, resulting in a null pointer dereference: Unable to handle kernel NULL pointer dereference Call Trace: do_kernel_fault+0x28/0x3c cpufreq_suspend+0xdc/0x160 device_shutdown+0x18/0x200 kernel_restart+0x40/0x80 arm64_sys_reboot+0x1b0/0x200 Fix this by adding cpus_read_lock()/cpus_read_unlock() to cpufreq_suspend() to block CPU hotplug operations while suspend is in pro... | CVSS3: 5.5 | 0% Низкий | 3 месяца назад | |
CVE-2026-64373 In the Linux kernel, the following vulnerability has been resolved: cpufreq: Fix hotplug-suspend race during reboot During system reboot, cpufreq_suspend() is called via the kernel_restart() -> device_shutdown() path. Unlike the normal system suspend path, the reboot path does not call freeze_processes(), so userspace processes and kernel threads remain active. This allows CPU hotplug operations to run concurrently with cpufreq_suspend(). The original code has no synchronization with CPU hotplug, leading to a race condition where governor_data can be freed by the hotplug path while cpufreq_suspend() is still accessing it, resulting in a null pointer dereference: Unable to handle kernel NULL pointer dereference Call Trace: do_kernel_fault+0x28/0x3c cpufreq_suspend+0xdc/0x160 device_shutdown+0x18/0x200 kernel_restart+0x40/0x80 arm64_sys_reboot+0x1b0/0x200 Fix this by adding cpus_read_lock()/cpus_read_unlock() to cpufreq_suspend() to block CPU hotplug operations wh | CVSS3: 4.7 | 0% Низкий | 3 месяца назад | |
CVE-2026-64373 cpufreq: Fix hotplug-suspend race during reboot | CVSS3: 4.7 | 0% Низкий | 3 месяца назад | |
CVE-2026-64373 In the Linux kernel, the following vulnerability has been resolved: c ... | CVSS3: 4.7 | 0% Низкий | 3 месяца назад | |
ROS-20261008-80-0280 Уязвимость kernel-lt | CVSS3: 4.7 | 0% Низкий | 18 дней назад | |
ROS-20261008-73-0281 Уязвимость kernel-lt | CVSS3: 4.7 | 0% Низкий | 18 дней назад | |
GHSA-r493-vrrx-v3x2 In the Linux kernel, the following vulnerability has been resolved: cpufreq: Fix hotplug-suspend race during reboot During system reboot, cpufreq_suspend() is called via the kernel_restart() -> device_shutdown() path. Unlike the normal system suspend path, the reboot path does not call freeze_processes(), so userspace processes and kernel threads remain active. This allows CPU hotplug operations to run concurrently with cpufreq_suspend(). The original code has no synchronization with CPU hotplug, leading to a race condition where governor_data can be freed by the hotplug path while cpufreq_suspend() is still accessing it, resulting in a null pointer dereference: Unable to handle kernel NULL pointer dereference Call Trace: do_kernel_fault+0x28/0x3c cpufreq_suspend+0xdc/0x160 device_shutdown+0x18/0x200 kernel_restart+0x40/0x80 arm64_sys_reboot+0x1b0/0x200 Fix this by adding cpus_read_lock()/cpus_read_unlock() to cpufreq_suspend() to block CPU hotplug operations... | CVSS3: 4.7 | 0% Низкий | 3 месяца назад | |
ALT-PU-2019-3291 ALT-PU-2019-3291: package `kernel-image-un-def` update to version 5.4.0-alt1 | CVSS3: 7.8 | почти 7 лет назад | ||
ALT-PU-2026-11928 ALT-PU-2026-11928: package `kernel-image-std-def` update to version 5.10.262-alt1 | CVSS3: 9.8 | 3 месяца назад | ||
ALT-PU-2026-11926 ALT-PU-2026-11926: package `kernel-image-un-def` update to version 6.1.180-alt1 | CVSS3: 9.8 | 2 месяца назад | ||
ALT-PU-2026-12325 ALT-PU-2026-12325: package `kernel-image-for-vm` update to version 6.18.40-alt1 | CVSS3: 9.8 | 3 месяца назад | ||
SUSE-SU-2026:4687-1 Security update for the Linux Kernel | 11 дней назад | |||
ALT-PU-2026-11249 ALT-PU-2026-11249: package `kernel-image-6.12` update to version 6.12.96-alt1 | CVSS3: 10 | 3 месяца назад | ||
ALT-PU-2026-11606 ALT-PU-2026-11606: package `kernel-image-6.18` update to version 6.18.40-alt1 | CVSS3: 10 | 3 месяца назад | ||
SUSE-SU-2026:4706-1 Security update for the Linux Kernel | 10 дней назад | |||
SUSE-SU-2026:4640-1 Security update for the Linux Kernel | 13 дней назад | |||
ELSA-2026-500249 ELSA-2026-500249: Unbreakable Enterprise kernel security update (IMPORTANT) | около 2 месяцев назад | |||
openSUSE-SU-2026:21910-1 Security update for the Linux Kernel | около 1 месяца назад | |||
ELSA-2026-500248 ELSA-2026-500248: Unbreakable Enterprise kernel security update (IMPORTANT) | около 2 месяцев назад |
Уязвимостей на страницу