cve.bz

CVE-2026-98861 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-98861 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98861?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98861?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-98861 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-98861

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-98861](https://cve.bz/cve/badge/CVE-2026-98861.svg)](https://cve.bz/cve/CVE-2026-98861)

HTML:

<a href="https://cve.bz/cve/CVE-2026-98861"><img src="https://cve.bz/cve/badge/CVE-2026-98861.svg" alt="CVE-2026-98861"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 6.18.34 before 6.18.56
Linuxfrom 7.0.11 before 7.1
Linux7.1 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.56
Linux7.27.2.10
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux7.2.10-1DEBIAN-CVE-2026-98861
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-98861
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-98861
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-98861
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-98861
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-98861 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-98861 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-98861 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-43.43~24.04.1UBUNTU-CVE-2026-98861 USN-9018-2
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-98861 USN-9020-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 25 moreno fix listedUBUNTU-CVE-2026-98861
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-43.43.1~24.04.2UBUNTU-CVE-2026-98861
Ubuntu26.04:LTSlinux7.0.0-43.43UBUNTU-CVE-2026-98861 USN-9018-1
11 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquitastreamlinux-lts6.18.58-r0BELL-CVE-2026-98861

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A race in fprobe unregistration can cause a use after free because standard RCU grace periods do not wait for an in flight handler that runs while RCU is not watching. An fprobe object may therefore be freed after unregister_fprobe or unregister_fprobe_async while a handler executing in an idle loop or nohz_full state still references it. The demonstrated and most likely consequence is temporal memory corruption followed by a kernel crash. For the CVSS the PR:L value in the paranoid score reflects a restricted tracing or BPF capable local process that can manage multi kprobes without full system administration rights. Typical systems restrict these operations to root or processes with CAP_BPF, CAP_PERFMON, or CAP_SYS_ADMIN, so the realistic base score uses PR:H. The race requires a narrow timing condition and handler execution while RCU is not watching, so AC:H is appropriate. The issue is local and is not network reachable.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-98861.

References

Check your stackJSON