Поиск уязвимостей
Количество 25
Количество 25
CVE-2025-68214
In the Linux kernel, the following vulnerability has been resolved: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0 CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer is pending while its function set to NULL. // next timer trigger <SOFTIR...
CVE-2025-68214
In the Linux kernel, the following vulnerability has been resolved: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer is pending while its function set to NULL. // next timer trigger <SOFTIRQ> ex...
CVE-2025-68214
In the Linux kernel, the following vulnerability has been resolved: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0 CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer
CVE-2025-68214
timers: Fix NULL function pointer race in timer_shutdown_sync()
CVE-2025-68214
In the Linux kernel, the following vulnerability has been resolved: t ...
RLSA-2026:49870
Low: kernel security, bug fix, and enhancement update
GHSA-q35m-cwfx-j6jx
In the Linux kernel, the following vulnerability has been resolved: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0 CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now ti...
ELSA-2026-49870
ELSA-2026-49870: kernel security, bug fix, and enhancement update (LOW)
BDU:2026-10636
Уязвимость функции __try_to_del_timer_sync() модуля kernel/time/timer.c подсистемы таймера ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260929-80-0002
Уязвимость kernel-lt
ROS-20260929-73-0002
Уязвимость kernel-lt
RLSA-2026:49871
Moderate: kernel security, bug fix, and enhancement update
ELSA-2026-49871
ELSA-2026-49871: kernel security, bug fix, and enhancement update (MODERATE)
ALT-PU-2025-17066
ALT-PU-2025-17066: package `kernel-image-un-def` update to version 6.1.159-alt1
ALT-PU-2025-17068
ALT-PU-2025-17068: package `kernel-image-rt` update to version 6.12.61-alt1
ALT-PU-2025-17067
ALT-PU-2025-17067: package `kernel-image-6.12` update to version 6.12.61-alt1
SUSE-SU-2026:4369-1
Security update for the Linux Kernel
ELSA-2026-50112
ELSA-2026-50112: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2026:4282-1
Security update for the Linux Kernel
SUSE-SU-2026:4254-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2025-68214 In the Linux kernel, the following vulnerability has been resolved: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0 CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer is pending while its function set to NULL. // next timer trigger <SOFTIR... | CVSS3: 4.7 | 0% Низкий | 11 месяцев назад |
 | CVE-2025-68214 In the Linux kernel, the following vulnerability has been resolved: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer is pending while its function set to NULL. // next timer trigger <SOFTIRQ> ex... | CVSS3: 5.5 | 0% Низкий | 11 месяцев назад |
 | CVE-2025-68214 In the Linux kernel, the following vulnerability has been resolved: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0 CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer | CVSS3: 4.7 | 0% Низкий | 11 месяцев назад |
 | CVE-2025-68214 timers: Fix NULL function pointer race in timer_shutdown_sync() | CVSS3: 4.7 | 0% Низкий | 11 месяцев назад |
| CVE-2025-68214 In the Linux kernel, the following vulnerability has been resolved: t ... | CVSS3: 4.7 | 0% Низкий | 11 месяцев назад |
 | RLSA-2026:49870 Low: kernel security, bug fix, and enhancement update | 0% Низкий | 3 месяца назад | |
| GHSA-q35m-cwfx-j6jx In the Linux kernel, the following vulnerability has been resolved: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0 CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now ti... | CVSS3: 4.7 | 0% Низкий | 11 месяцев назад |
| ELSA-2026-49870 ELSA-2026-49870: kernel security, bug fix, and enhancement update (LOW) | 0% Низкий | 3 месяца назад | |
 | BDU:2026-10636 Уязвимость функции __try_to_del_timer_sync() модуля kernel/time/timer.c подсистемы таймера ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | 12 месяцев назад |
 | ROS-20260929-80-0002 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад |
| ROS-20260929-73-0002 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад |
| RLSA-2026:49871 Moderate: kernel security, bug fix, and enhancement update | 3 месяца назад | ||
| ELSA-2026-49871 ELSA-2026-49871: kernel security, bug fix, and enhancement update (MODERATE) | 3 месяца назад | ||
| ALT-PU-2025-17066 ALT-PU-2025-17066: package `kernel-image-un-def` update to version 6.1.159-alt1 | CVSS3: 5.5 | 0% Низкий | 11 месяцев назад |
| ALT-PU-2025-17068 ALT-PU-2025-17068: package `kernel-image-rt` update to version 6.12.61-alt1 | CVSS3: 7.5 | 11 месяцев назад | |
| ALT-PU-2025-17067 ALT-PU-2025-17067: package `kernel-image-6.12` update to version 6.12.61-alt1 | CVSS3: 7.5 | 11 месяцев назад | |
 | SUSE-SU-2026:4369-1 Security update for the Linux Kernel | около 1 месяца назад | ||
| ELSA-2026-50112 ELSA-2026-50112: Unbreakable Enterprise kernel security update (IMPORTANT) | 9 месяцев назад | ||
| SUSE-SU-2026:4282-1 Security update for the Linux Kernel | около 2 месяцев назад | ||
| SUSE-SU-2026:4254-1 Security update for the Linux Kernel | около 2 месяцев назад |
Уязвимостей на страницу