CVE-2026-98536: Linux kernel · writeback: report a Tasks-RCU quiescent state per cgwb drain pass
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fd3bf32279df98751364b3609eb100a3e42f253b : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fd3bf32279df98751364b3609eb100a3e42f253b, ebf1555ad2821be06f87a88ffd9a2cab8d2200e1, 863049b4018237d1590cd13b16e9fe9c0faad2c6 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix has been implemented in the Linux kernel source as indicated by multiple fixed commit hashes. Users should update to a kernel version including these fixes to resolve the issue. No additional mitigation is required once the fixed kernel is deployed.
Description
CVE-2026-98536 is a Linux kernel vulnerability affecting version 5.14 where a long-running writeback drain loop on certain kernel configurations can cause a system hang and panic. The issue arises because the kernel does not properly report a Tasks-RCU quiescent state during the drain loop under specific preemption modes, leading to stalled tasks and potential host panic. The flaw was fixed by ensuring the kernel calls cond_resched_tasks_rcu_qs() during the drain loop to avoid stalling synchronize_rcu_tasks() callers.
References
- git.kernel.org/stable/c/863049b4018237d1590cd13b16e9fe9c0faad2c6 (opens in a new tab)
- git.kernel.org/stable/c/42462b5bb0dec57db7f85d0f77655c737d45754d (opens in a new tab)
- git.kernel.org/stable/c/ebf1555ad2821be06f87a88ffd9a2cab8d2200e1 (opens in a new tab)
- git.kernel.org/stable/c/4eb889649eaf65f4a5727b04ba1c017b7d05bb16 (opens in a new tab)
- git.kernel.org/stable/c/fd3bf32279df98751364b3609eb100a3e42f253b (opens in a new tab)
- git.kernel.org/stable/c/260f586a80e7f624dd7f069898a75a904f34d373 (opens in a new tab)
- git.kernel.org/stable/c/407a5d205179a4ab186571b0e16ec42725dc77bc (opens in a new tab)