CVE-2026-98861 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
- 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
- Linux Linux: fixed in 6.18.56
- Linux Linux: fixed in 7.2.10
- Linux Linux: fixed in 7.3
- Debian, Ubuntu, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain 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.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | from 6.18.34 before 6.18.56 |
| Linux | from 7.0.11 before 7.1 |
| Linux | 7.1 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.18 | 6.18.56 |
| Linux | 7.2 | 7.2.10 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.2.10-1 | DEBIAN-CVE-2026-98861 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-98861 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-98861 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-98861 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-98861 |
| Ubuntu | 24.04:LTS | linux-aws-7.0 | 7.0.0-1017.18~24.04.1 | UBUNTU-CVE-2026-98861 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1019.19~24.04.1 | UBUNTU-CVE-2026-98861 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-gcp-7.0 | 7.0.0-1017.19~24.04.1 | UBUNTU-CVE-2026-98861 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-43.43~24.04.1 | UBUNTU-CVE-2026-98861 USN-9018-2 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1016.18~24.04.1 | UBUNTU-CVE-2026-98861 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 25 more | no fix listed | UBUNTU-CVE-2026-98861 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-43.43.1~24.04.2 | UBUNTU-CVE-2026-98861 |
| Ubuntu | 26.04:LTS | linux | 7.0.0-43.43 | UBUNTU-CVE-2026-98861 USN-9018-1 |
| 11 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Alpaquita | stream | linux-lts | 6.18.58-r0 | BELL-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.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix 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.