Количество 26
Количество 26

CVE-2025-38352
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.

CVE-2025-38352
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.

CVE-2025-38352
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.

CVE-2025-38352
CVE-2025-38352
In the Linux kernel, the following vulnerability has been resolved: p ...
GHSA-mr4j-mh66-4679
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.
ELSA-2025-15662
ELSA-2025-15662: kernel security update (IMPORTANT)

BDU:2025-10870
Уязвимость функции handle_posix_cpu_timers ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ELSA-2025-15648
ELSA-2025-15648: kernel security update (IMPORTANT)
ELSA-2025-15471
ELSA-2025-15471: kernel security update (IMPORTANT)
ELSA-2025-15661
ELSA-2025-15661: kernel security update (IMPORTANT)

SUSE-SU-2025:03314-1
Security update for the Linux Kernel

ROS-20250902-01
Множественные уязвимости kernel-lt

SUSE-SU-2025:03310-1
Security update for the Linux Kernel

SUSE-SU-2025:03344-1
Security update for the Linux Kernel
ELSA-2025-20553
ELSA-2025-20553: Unbreakable Enterprise kernel security update (IMPORTANT)

SUSE-SU-2025:03204-1
Security update for the Linux Kernel
ELSA-2025-20552
ELSA-2025-20552: Unbreakable Enterprise kernel security update (IMPORTANT)

SUSE-SU-2025:03023-1
Security update for the Linux Kernel

SUSE-SU-2025:02996-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
---|---|---|---|---|
![]() | CVE-2025-38352 In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case. | CVSS3: 7.4 | 1% Низкий | 2 месяца назад |
![]() | CVE-2025-38352 In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case. | CVSS3: 7.8 | 1% Низкий | 2 месяца назад |
![]() | CVE-2025-38352 In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case. | CVSS3: 7.4 | 1% Низкий | 2 месяца назад |
![]() | 1% Низкий | около 2 месяцев назад | ||
CVE-2025-38352 In the Linux kernel, the following vulnerability has been resolved: p ... | CVSS3: 7.4 | 1% Низкий | 2 месяца назад | |
GHSA-mr4j-mh66-4679 In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case. | CVSS3: 7.4 | 1% Низкий | 2 месяца назад | |
ELSA-2025-15662 ELSA-2025-15662: kernel security update (IMPORTANT) | 20 дней назад | |||
![]() | BDU:2025-10870 Уязвимость функции handle_posix_cpu_timers ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 4.6 | 1% Низкий | 2 месяца назад |
ELSA-2025-15648 ELSA-2025-15648: kernel security update (IMPORTANT) | 7 дней назад | |||
ELSA-2025-15471 ELSA-2025-15471: kernel security update (IMPORTANT) | 23 дня назад | |||
ELSA-2025-15661 ELSA-2025-15661: kernel security update (IMPORTANT) | 20 дней назад | |||
![]() | SUSE-SU-2025:03314-1 Security update for the Linux Kernel | 8 дней назад | ||
![]() | ROS-20250902-01 Множественные уязвимости kernel-lt | CVSS3: 5.5 | около 1 месяца назад | |
![]() | SUSE-SU-2025:03310-1 Security update for the Linux Kernel | 9 дней назад | ||
![]() | SUSE-SU-2025:03344-1 Security update for the Linux Kernel | 8 дней назад | ||
ELSA-2025-20553 ELSA-2025-20553: Unbreakable Enterprise kernel security update (IMPORTANT) | 23 дня назад | |||
![]() | SUSE-SU-2025:03204-1 Security update for the Linux Kernel | 20 дней назад | ||
ELSA-2025-20552 ELSA-2025-20552: Unbreakable Enterprise kernel security update (IMPORTANT) | 24 дня назад | |||
![]() | SUSE-SU-2025:03023-1 Security update for the Linux Kernel | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02996-1 Security update for the Linux Kernel | около 1 месяца назад |
Уязвимостей на страницу