Поиск уязвимостей
Количество 21
Количество 21
CVE-2025-39744
In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. Fix by managing the irq_work state correctly. irq_exit() __irq_exit_rcu() /* in_hardirq() returns false after this */ preempt_count_sub(HARDIRQ_OFFSET) tick_irq_exit() tick_nohz_irq_exit() tick_nohz_stop_sched_tick() trace_tick_stop() /* a bpf prog is hooked on this trace point */ __bpf_trace_tick_stop() bpf_trace_run2() rcu_read_unlock_special() /* will send a IPI to itself */ irq_work_queue_on(&rdp->defer_qs_iw, rdp->cpu); A simple reproducer can also be obtained by doing the following in tick_irq_exit(). It will hang on boot without the patch...
CVE-2025-39744
In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. Fix by managing the irq_work state correctly. irq_exit() __irq_exit_rcu() /* in_hardirq() returns false after this */ preempt_count_sub(HARDIRQ_OFFSET) tick_irq_exit() tick_nohz_irq_exit() tick_nohz_stop_sched_tick() trace_tick_stop() /* a bpf prog is hooked on this trace point */ __bpf_trace_tick_stop() bpf_trace_run2() rcu_read_unlock_special() /* will send a IPI to itself */ irq_work_queue_on(&rdp->defer_qs_iw, rdp->cpu); A simple reproducer can also be obtained by doing the following in tick_irq_exit(). It will hang on boot without the patch...
CVE-2025-39744
In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. Fix by managing the irq_work state correctly. irq_exit() __irq_exit_rcu() /* in_hardirq() returns false after this */ preempt_count_sub(HARDIRQ_OFFSET) tick_irq_exit() tick_nohz_irq_exit() tick_nohz_stop_sched_tick() trace_tick_stop() /* a bpf prog is hooked on this trace point */ __bpf_trace_tick_stop() bpf_trace_run2() rcu_read_unlock_special() /* will send a IPI to itself */ irq_work_queue_on(&rdp->defer_qs_iw, rdp->cpu); A simple reproducer can also
CVE-2025-39744
rcu: Fix rcu_read_unlock() deadloop due to IRQ work
CVE-2025-39744
In the Linux kernel, the following vulnerability has been resolved: r ...
GHSA-vqg7-j8rg-9mw8
In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. Fix by managing the irq_work state correctly. irq_exit() __irq_exit_rcu() /* in_hardirq() returns false after this */ preempt_count_sub(HARDIRQ_OFFSET) tick_irq_exit() tick_nohz_irq_exit() tick_nohz_stop_sched_tick() trace_tick_stop() /* a bpf prog is hooked on this trace point */ __bpf_trace_tick_stop() bpf_trace_run2() rcu_read_unlock_special() /* will send a IPI to itself */ irq_work_queue_on(&rdp->defer_qs_iw, rdp->cpu); A simple reproducer can al...
BDU:2026-01275
Уязвимость функции rcu_read_unlock_special() модуля kernel/rcu/tree_plugin.h ядра операционной системы Linux, позволяющая нарушителю получить доступ к защищаемой информации или вызвать отказ в обслуживании
SUSE-SU-2025:3725-1
Security update for the Linux Kernel
SUSE-SU-2025:03601-1
Security update for the Linux Kernel
ELSA-2025-20662
ELSA-2025-20662: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2025:03633-1
Security update for the Linux Kernel
ALT-PU-2025-16510
ALT-PU-2025-16510: package `kernel-image-6.12` update to version 6.12.45-alt1
ALT-PU-2025-16465
ALT-PU-2025-16465: package `kernel-image-rt` update to version 6.12.45-alt1
SUSE-SU-2025:3751-1
Security update for the Linux Kernel
SUSE-SU-2025:03600-1
Security update for the Linux Kernel
SUSE-SU-2025:03634-1
Security update for the Linux Kernel
openSUSE-SU-2025:20081-1
Security update for the Linux Kernel
openSUSE-SU-2025-20011-1
Security update for the Linux Kernel
ALT-PU-2026-1529
ALT-PU-2026-1529: package `kernel-image-pine` update to version 6.12.66-alt1
ALT-PU-2025-12647
ALT-PU-2025-12647: package `kernel-image-rpi-un` update to version 6.12.49-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-39744 In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. Fix by managing the irq_work state correctly. irq_exit() __irq_exit_rcu() /* in_hardirq() returns false after this */ preempt_count_sub(HARDIRQ_OFFSET) tick_irq_exit() tick_nohz_irq_exit() tick_nohz_stop_sched_tick() trace_tick_stop() /* a bpf prog is hooked on this trace point */ __bpf_trace_tick_stop() bpf_trace_run2() rcu_read_unlock_special() /* will send a IPI to itself */ irq_work_queue_on(&rdp->defer_qs_iw, rdp->cpu); A simple reproducer can also be obtained by doing the following in tick_irq_exit(). It will hang on boot without the patch... | CVSS3: 7.1 | 0% Низкий | около 1 года назад | |
CVE-2025-39744 In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. Fix by managing the irq_work state correctly. irq_exit() __irq_exit_rcu() /* in_hardirq() returns false after this */ preempt_count_sub(HARDIRQ_OFFSET) tick_irq_exit() tick_nohz_irq_exit() tick_nohz_stop_sched_tick() trace_tick_stop() /* a bpf prog is hooked on this trace point */ __bpf_trace_tick_stop() bpf_trace_run2() rcu_read_unlock_special() /* will send a IPI to itself */ irq_work_queue_on(&rdp->defer_qs_iw, rdp->cpu); A simple reproducer can also be obtained by doing the following in tick_irq_exit(). It will hang on boot without the patch... | 0% Низкий | около 1 года назад | ||
CVE-2025-39744 In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. Fix by managing the irq_work state correctly. irq_exit() __irq_exit_rcu() /* in_hardirq() returns false after this */ preempt_count_sub(HARDIRQ_OFFSET) tick_irq_exit() tick_nohz_irq_exit() tick_nohz_stop_sched_tick() trace_tick_stop() /* a bpf prog is hooked on this trace point */ __bpf_trace_tick_stop() bpf_trace_run2() rcu_read_unlock_special() /* will send a IPI to itself */ irq_work_queue_on(&rdp->defer_qs_iw, rdp->cpu); A simple reproducer can also | CVSS3: 7.1 | 0% Низкий | около 1 года назад | |
CVE-2025-39744 rcu: Fix rcu_read_unlock() deadloop due to IRQ work | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2025-39744 In the Linux kernel, the following vulnerability has been resolved: r ... | CVSS3: 7.1 | 0% Низкий | около 1 года назад | |
GHSA-vqg7-j8rg-9mw8 In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. Fix by managing the irq_work state correctly. irq_exit() __irq_exit_rcu() /* in_hardirq() returns false after this */ preempt_count_sub(HARDIRQ_OFFSET) tick_irq_exit() tick_nohz_irq_exit() tick_nohz_stop_sched_tick() trace_tick_stop() /* a bpf prog is hooked on this trace point */ __bpf_trace_tick_stop() bpf_trace_run2() rcu_read_unlock_special() /* will send a IPI to itself */ irq_work_queue_on(&rdp->defer_qs_iw, rdp->cpu); A simple reproducer can al... | CVSS3: 7.1 | 0% Низкий | около 1 года назад | |
BDU:2026-01275 Уязвимость функции rcu_read_unlock_special() модуля kernel/rcu/tree_plugin.h ядра операционной системы Linux, позволяющая нарушителю получить доступ к защищаемой информации или вызвать отказ в обслуживании | CVSS3: 7.1 | 0% Низкий | больше 1 года назад | |
SUSE-SU-2025:3725-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03601-1 Security update for the Linux Kernel | около 1 года назад | |||
ELSA-2025-20662 ELSA-2025-20662: Unbreakable Enterprise kernel security update (IMPORTANT) | около 1 года назад | |||
SUSE-SU-2025:03633-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2025-16510 ALT-PU-2025-16510: package `kernel-image-6.12` update to version 6.12.45-alt1 | CVSS3: 9.8 | около 1 года назад | ||
ALT-PU-2025-16465 ALT-PU-2025-16465: package `kernel-image-rt` update to version 6.12.45-alt1 | CVSS3: 9.8 | около 1 года назад | ||
SUSE-SU-2025:3751-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03600-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03634-1 Security update for the Linux Kernel | около 1 года назад | |||
openSUSE-SU-2025:20081-1 Security update for the Linux Kernel | 12 месяцев назад | |||
openSUSE-SU-2025-20011-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2026-1529 ALT-PU-2026-1529: package `kernel-image-pine` update to version 6.12.66-alt1 | CVSS3: 9.8 | 10 месяцев назад | ||
ALT-PU-2025-12647 ALT-PU-2025-12647: package `kernel-image-rpi-un` update to version 6.12.49-alt1 | CVSS3: 9.8 | около 1 года назад |
Уязвимостей на страницу