CVE-2026-98861: Linux kernel · fprobe: Use guard(rcu_sched_notrace) and check rcu_is_watching()
Source GCVE Database
Not known to be exploited · fixed in e0a6249190402a28f1e2925a81acf573157d55ef : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e0a6249190402a28f1e2925a81acf573157d55ef, dd4a0d4993633b45470abf6da4ea0ca563402245, a85d0f00671b4d4527317c10ba018680f7d8d673 +2
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– |
AI-suggested
A fix for this vulnerability has been implemented in the Linux kernel by introducing guard(rcu_sched_notrace) and checks for rcu_is_watching() in fprobe handlers to ensure safe synchronization and prevent use-after-free. Users should update to the fixed kernel versions once available.
Description
A use-after-free vulnerability in the Linux kernel's fprobe subsystem has been resolved. The issue arises because unregister_fprobe() and unregister_fprobe_async() rely on standard RCU grace periods that do not track execution when RCU is not watching, such as in idle or nohz_full states. This can lead to use-after-free if an fprobe handler runs during these states after unregistration. The fix involves using guard(rcu_sched_notrace) and checking rcu_is_watching() to ensure handlers exit early when RCU is not watching, and reducing lockdep overhead by replacing rcu_read_lock() with rcu_read_lock_sched_notrace() where appropriate.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98861 (opens in a new tab)
- git.kernel.org/stable/c/a85d0f00671b4d4527317c10ba018680f7d8d673 (opens in a new tab)
- git.kernel.org/stable/c/dd4a0d4993633b45470abf6da4ea0ca563402245 (opens in a new tab)
- git.kernel.org/stable/c/e0a6249190402a28f1e2925a81acf573157d55ef (opens in a new tab)