https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 02 Nov 2026 21:28:05 +0000 https://db.gcve.eu/vuln/certfr-2026-avi-1375 certfr-2026-avi-1375 https://db.gcve.eu/vuln/certfr-2026-avi-1375 https://db.gcve.eu/vuln/fkie_cve-2026-98536 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>writeback: report a Tasks-RCU quiescent state per cgwb drain pass</p> <p>cleanup_offline_cgwbs_workfn() drains a dying cgwb by calling cleanup_offline_cgwb() until it returns false, with a cond_resched() between passes. On a CONFIG_PREEMPTION kernel that cond_resched() does nothing: _cond_resched() is a plain &#34;return 0&#34;, and under PREEMPT_DYNAMIC the full and lazy modes disable it. Since commit 7dadeaa6e851 (&#34;sched: Further restrict the preemption modes&#34;) those are the only two models on the architectures with PREEMPT_LAZY support, arm64 and x86 among them, so the drain loop never reports a Tasks-RCU quiescent state.</p> <p>A worker draining a cgwb with millions of attached inodes runs for minutes. On a 6.18 arm64 host in lazy mode the cgwb worker drained one dying cgroup&#39;s writeback domain for over 11 minutes. A BPF program unlink (bpf_trampoline_unlink_prog -&gt; bpf_trampoline_update -&gt; unregister_ftrace_direct -&gt; ftrace_shutdown -&gt; synchronize_rcu_tasks()) waited on that grace period while holding the trampoline mutex, 42 tasks queued behind it in D state, and the hung task detector fired at 614 s and panicked the host. Any BPF or ftrace detach during a long drain inherits the drain&#39;s length.</p> <p>Fix this by calling cond_resched_tasks_rcu_qs() so we do not stall out anybody who calls sycnrhonize_rcu_tasks(). We put this in a do { } while loop because if we have many small cgroups cleanup_offline_cgwb() will return…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>writeback: report a Tasks-RCU quiescent state per cgwb drain pass</p> <p>cleanup_offline_cgwbs_workfn() drains a dying cgwb by calling cleanup_offline_cgwb() until it returns false, with a cond_resched() between passes. On a CONFIG_PREEMPTION kernel that cond_resched() does nothing: _cond_resched() is a plain &#34;return 0&#34;, and under PREEMPT_DYNAMIC the full and lazy modes disable it. Since commit 7dadeaa6e851 (&#34;sched: Further restrict the preemption modes&#34;) those are the only two models on the architectures with PREEMPT_LAZY support, arm64 and x86 among them, so the drain loop never reports a Tasks-RCU quiescent state.</p> <p>A worker draining a cgwb with millions of attached inodes runs for minutes. On a 6.18 arm64 host in lazy mode the cgwb worker drained one dying cgroup&#39;s writeback domain for over 11 minutes. A BPF program unlink (bpf_trampoline_unlink_prog -&gt; bpf_trampoline_update -&gt; unregister_ftrace_direct -&gt; ftrace_shutdown -&gt; synchronize_rcu_tasks()) waited on that grace period while holding the trampoline mutex, 42 tasks queued behind it in D state, and the hung task detector fired at 614 s and panicked the host. Any BPF or ftrace detach during a long drain inherits the drain&#39;s length.</p> <p>Fix this by calling cond_resched_tasks_rcu_qs() so we do not stall out anybody who calls sycnrhonize_rcu_tasks(). We put this in a do { } while loop because if we have many small cgroups cleanup_offline_cgwb() will return…</p> https://db.gcve.eu/vuln/fkie_cve-2026-98536 https://db.gcve.eu/vuln/ghsa-hq8j-r79p-42p5 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>writeback: report a Tasks-RCU quiescent state per cgwb drain pass</p> <p>cleanup_offline_cgwbs_workfn() drains a dying cgwb by calling cleanup_offline_cgwb() until it returns false, with a cond_resched() between passes. On a CONFIG_PREEMPTION kernel that cond_resched() does nothing: _cond_resched() is a plain &#34;return 0&#34;, and under PREEMPT_DYNAMIC the full and lazy modes disable it. Since commit 7dadeaa6e851 (&#34;sched: Further restrict the preemption modes&#34;) those are the only two models on the architectures with PREEMPT_LAZY support, arm64 and x86 among them, so the drain loop never reports a Tasks-RCU quiescent state.</p> <p>A worker draining a cgwb with millions of attached inodes runs for minutes. On a 6.18 arm64 host in lazy mode the cgwb worker drained one dying cgroup&#39;s writeback domain for over 11 minutes. A BPF program unlink (bpf_trampoline_unlink_prog -&gt; bpf_trampoline_update -&gt; unregister_ftrace_direct -&gt; ftrace_shutdown -&gt; synchronize_rcu_tasks()) waited on that grace period while holding the trampoline mutex, 42 tasks queued behind it in D state, and the hung task detector fired at 614 s and panicked the host. Any BPF or ftrace detach during a long drain inherits the drain&#39;s length.</p> <p>Fix this by calling cond_resched_tasks_rcu_qs() so we do not stall out anybody who calls sycnrhonize_rcu_tasks(). We put this in a do { } while loop because if we have many small cgroups cleanup_offline_cgwb() will return…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>writeback: report a Tasks-RCU quiescent state per cgwb drain pass</p> <p>cleanup_offline_cgwbs_workfn() drains a dying cgwb by calling cleanup_offline_cgwb() until it returns false, with a cond_resched() between passes. On a CONFIG_PREEMPTION kernel that cond_resched() does nothing: _cond_resched() is a plain &#34;return 0&#34;, and under PREEMPT_DYNAMIC the full and lazy modes disable it. Since commit 7dadeaa6e851 (&#34;sched: Further restrict the preemption modes&#34;) those are the only two models on the architectures with PREEMPT_LAZY support, arm64 and x86 among them, so the drain loop never reports a Tasks-RCU quiescent state.</p> <p>A worker draining a cgwb with millions of attached inodes runs for minutes. On a 6.18 arm64 host in lazy mode the cgwb worker drained one dying cgroup&#39;s writeback domain for over 11 minutes. A BPF program unlink (bpf_trampoline_unlink_prog -&gt; bpf_trampoline_update -&gt; unregister_ftrace_direct -&gt; ftrace_shutdown -&gt; synchronize_rcu_tasks()) waited on that grace period while holding the trampoline mutex, 42 tasks queued behind it in D state, and the hung task detector fired at 614 s and panicked the host. Any BPF or ftrace detach during a long drain inherits the drain&#39;s length.</p> <p>Fix this by calling cond_resched_tasks_rcu_qs() so we do not stall out anybody who calls sycnrhonize_rcu_tasks(). We put this in a do { } while loop because if we have many small cgroups cleanup_offline_cgwb() will return…</p> https://db.gcve.eu/vuln/ghsa-hq8j-r79p-42p5 https://db.gcve.eu/vuln/msrc_cve-2026-98536 msrc_CVE-2026-98536 https://db.gcve.eu/vuln/msrc_cve-2026-98536 https://db.gcve.eu/vuln/ubuntu-cve-2026-98536 <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 193 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: writeback: report a Tasks-RCU quiescent state per cgwb drain pass cleanup_offline_cgwbs_workfn() drains a dying cgwb by calling cleanup_offline_cgwb() until it returns false, with a cond_resched() between passes. On a CONFIG_PREEMPTION kernel that cond_resched() does nothing: _cond_resched() is a plain &#34;return 0&#34;, and under PREEMPT_DYNAMIC the full and lazy modes disable it. Since commit 7dadeaa6e851 (&#34;sched: Further restrict the preemption modes&#34;) those are the only two models on the architectures with PREEMPT_LAZY support, arm64 and x86 among them, so the drain loop never reports a Tasks-RCU quiescent state. A worker draining a cgwb with millions of attached inodes runs for minutes. On a 6.18 arm64 host in lazy mode the cgwb worker drained one dying cgroup&#39;s writeback domain for over 11 minutes. A BPF program unlink (bpf_trampoline_unlink_prog -&gt; bpf_trampoline_update -&gt; unregister_ftrace_direct -&gt; ftrace_shutdown -&gt; synchronize_rcu_tasks()) waited on that grace period while holding the trampoline mutex, 42 tasks queued behind it in D state, and the hung task detector fired at 614 s and panicked the host. Any BPF or ftrace detach during a long drain inherits the drain&#39;s length. Fix this by calling cond_resched_tasks_rcu_qs() so we do not stall out anybody who calls sycnrhonize_rcu_tasks(). We put this in a do { } while loop because if we have many small cgroups cleanup_offline_cgwb() will return fals…</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 193 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: writeback: report a Tasks-RCU quiescent state per cgwb drain pass cleanup_offline_cgwbs_workfn() drains a dying cgwb by calling cleanup_offline_cgwb() until it returns false, with a cond_resched() between passes. On a CONFIG_PREEMPTION kernel that cond_resched() does nothing: _cond_resched() is a plain &#34;return 0&#34;, and under PREEMPT_DYNAMIC the full and lazy modes disable it. Since commit 7dadeaa6e851 (&#34;sched: Further restrict the preemption modes&#34;) those are the only two models on the architectures with PREEMPT_LAZY support, arm64 and x86 among them, so the drain loop never reports a Tasks-RCU quiescent state. A worker draining a cgwb with millions of attached inodes runs for minutes. On a 6.18 arm64 host in lazy mode the cgwb worker drained one dying cgroup&#39;s writeback domain for over 11 minutes. A BPF program unlink (bpf_trampoline_unlink_prog -&gt; bpf_trampoline_update -&gt; unregister_ftrace_direct -&gt; ftrace_shutdown -&gt; synchronize_rcu_tasks()) waited on that grace period while holding the trampoline mutex, 42 tasks queued behind it in D state, and the hung task detector fired at 614 s and panicked the host. Any BPF or ftrace detach during a long drain inherits the drain&#39;s length. Fix this by calling cond_resched_tasks_rcu_qs() so we do not stall out anybody who calls sycnrhonize_rcu_tasks(). We put this in a do { } while loop because if we have many small cgroups cleanup_offline_cgwb() will return fals…</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-98536 https://db.gcve.eu/vuln/wid-sec-w-2026-4019 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.</p> https://db.gcve.eu/vuln/wid-sec-w-2026-4019