CVE-2026-98536

writeback: report a Tasks-RCU quiescent state per cgwb drain pass

Description

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 "return 0", and under PREEMPT_DYNAMIC the full and lazy modes disable it. Since commit 7dadeaa6e851 ("sched: Further restrict the preemption modes") 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's writeback domain for over 11 minutes. A BPF program unlink (bpf_trampoline_unlink_prog -> bpf_trampoline_update -> unregister_ftrace_direct -> ftrace_shutdown -> 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'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 false and we will never call cond_resched_tasks_rcu_qs(), creating the same problem.

Key facts

Published
18 Oct 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.215% likely to be exploited in the next 30 days, higher than 11.974% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • c22d70a162d3cc177282c4487be4d54876ca55c8 up to but excluding 863049b4018237d1590cd13b16e9fe9c0faad2c6 (affected)
  • c22d70a162d3cc177282c4487be4d54876ca55c8 up to but excluding 42462b5bb0dec57db7f85d0f77655c737d45754d (affected)
  • c22d70a162d3cc177282c4487be4d54876ca55c8 up to but excluding ebf1555ad2821be06f87a88ffd9a2cab8d2200e1 (affected)
  • c22d70a162d3cc177282c4487be4d54876ca55c8 up to but excluding 4eb889649eaf65f4a5727b04ba1c017b7d05bb16 (affected)
  • c22d70a162d3cc177282c4487be4d54876ca55c8 up to but excluding fd3bf32279df98751364b3609eb100a3e42f253b (affected)
  • c22d70a162d3cc177282c4487be4d54876ca55c8 up to but excluding 260f586a80e7f624dd7f069898a75a904f34d373 (affected)
  • c22d70a162d3cc177282c4487be4d54876ca55c8 up to but excluding 407a5d205179a4ab186571b0e16ec42725dc77bc (affected)
LinuxLinux
  • Default status: affected
  • 5.14 (affected)
  • 0 up to but excluding 5.14 (unaffected)
  • 5.15.222 up to and including 5.15.* (unaffected)
  • 6.1.189 up to and including 6.1.* (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.55 up to and including 6.18.* (unaffected)
  • 7.2.9 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References