https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 11:35:24 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-15088 bdu:2025-15088 https://cve.radiocsirt.org/vuln/bdu:2025-15088 https://cve.radiocsirt.org/vuln/bell-cve-2024-50032 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2024-50032 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0349 certfr-2025-avi-0349 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0349 https://cve.radiocsirt.org/vuln/fkie_cve-2024-50032 <p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.</p> <p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-50032 https://cve.radiocsirt.org/vuln/ghsa-5m9v-h8pg-4xv6 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rcu/nocb: Fix rcuog wake-up from offline softirq</p> <p>After a CPU has set itself offline and before it eventually calls rcutree_report_cpu_dead(), there are still opportunities for callbacks to be enqueued, for example from a softirq. When that happens on NOCB, the rcuog wake-up is deferred through an IPI to an online CPU in order not to call into the scheduler and risk arming the RT-bandwidth after hrtimers have been migrated out and disabled.</p> <p>But performing a synchronized IPI from a softirq is buggy as reported in the following scenario:</p> <p>WARNING: CPU: 1 PID: 26 at kernel/smp.c:633 smp_call_function_single Modules linked in: rcutorture torture CPU: 1 UID: 0 PID: 26 Comm: migration/1 Not tainted 6.11.0-rc1-00012-g9139f93209d1 #1 Stopper: multi_cpu_stop+0x0/0x320 &lt;- __stop_cpus+0xd0/0x120 RIP: 0010:smp_call_function_single &lt;IRQ&gt; swake_up_one_online __call_rcu_nocb_wake __call_rcu_common ? rcu_torture_one_read call_timer_fn __run_timers run_timer_softirq handle_softirqs irq_exit_rcu ? tick_handle_periodic sysvec_apic_timer_interrupt &lt;/IRQ&gt;</p> <p>Fix this with forcing deferred rcuog wake up through the NOCB timer when the CPU is offline. The actual wake up will happen from rcutree_report_cpu_dead().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rcu/nocb: Fix rcuog wake-up from offline softirq</p> <p>After a CPU has set itself offline and before it eventually calls rcutree_report_cpu_dead(), there are still opportunities for callbacks to be enqueued, for example from a softirq. When that happens on NOCB, the rcuog wake-up is deferred through an IPI to an online CPU in order not to call into the scheduler and risk arming the RT-bandwidth after hrtimers have been migrated out and disabled.</p> <p>But performing a synchronized IPI from a softirq is buggy as reported in the following scenario:</p> <p>WARNING: CPU: 1 PID: 26 at kernel/smp.c:633 smp_call_function_single Modules linked in: rcutorture torture CPU: 1 UID: 0 PID: 26 Comm: migration/1 Not tainted 6.11.0-rc1-00012-g9139f93209d1 #1 Stopper: multi_cpu_stop+0x0/0x320 &lt;- __stop_cpus+0xd0/0x120 RIP: 0010:smp_call_function_single &lt;IRQ&gt; swake_up_one_online __call_rcu_nocb_wake __call_rcu_common ? rcu_torture_one_read call_timer_fn __run_timers run_timer_softirq handle_softirqs irq_exit_rcu ? tick_handle_periodic sysvec_apic_timer_interrupt &lt;/IRQ&gt;</p> <p>Fix this with forcing deferred rcuog wake up through the NOCB timer when the CPU is offline. The actual wake up will happen from rcutree_report_cpu_dead().</p> https://cve.radiocsirt.org/vuln/ghsa-5m9v-h8pg-4xv6 https://cve.radiocsirt.org/vuln/msrc_cve-2024-50032 msrc_CVE-2024-50032 https://cve.radiocsirt.org/vuln/msrc_cve-2024-50032 https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1 <p>kernel-devel-6.11.8-1.1 on GA media</p> <p>kernel-devel-6.11.8-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50032 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 86 more</p> <p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 86 more</p> <p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50032 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251