CVE-2026-98856 json
kprobes: Skip disarmed probes when checking optkprobe overlap
published 2026-10-18 21 d ago modified 2026-10-30 9 d ago also EUVD-2026-103796
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
kprobes: Skip disarmed probes when checking optkprobe overlap
On x86, an optkprobe at A replaces five bytes with a jump. If a disabled probe B is at A+2, get_optimized_kprobe() stops at B when arming a new probe C at A+4. It leaves A optimized:
A A+1 A+2 A+3 A+4 A's jump | e9 | d0 | d1 | d2 | d3 | after C | e9 | d0 | d1 | d2 | cc |
The INT3 for C overwrites the last byte of A's jump displacement, so execution can jump to the wrong address. B can have prepared optinsns while disarmed, but has no jump to unoptimize.
Continue past disarmed and unprepared probes to find the active optimized probe before arming a probe in its jump.
Patch / fix
- Linux Linux 5.10.273, 5.15.224, 6.1.191, 6.6.160, 6.12.113, 6.18.56, 7.2.10, 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.10-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98856
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-108723
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/e29e819cacfb4e3cd56d41eb704ab4718d6d2915 commit
- git.kernel.org/stable/c/ab9ed9faa67bf67383ff7e1479655e232a843c2b commit
- git.kernel.org/stable/c/3b0f604df9e2b9a456f1ae5266a439998c4c8826 commit
- git.kernel.org/stable/c/3f968dcdf018861129f97910fa7bd680d939a9b0 commit
- git.kernel.org/stable/c/985a568171e7bdba6dcde3420d0e5bb515813457 commit
- git.kernel.org/stable/c/6745fa65f4115045431c0c15610e876855a04625 commit
- git.kernel.org/stable/c/526fac219e8b7d3369b43026bd0a1df51b811cd4 commit
- git.kernel.org/stable/c/7a39c732a22ec4a369af9e19fbe3d666ec83eec4 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98856 updated cvss 4.4
kernel: kprobes: Skip disarmed probes when checking optkprobe overlap
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/e29e819cacfb4e3cd56d41eb704ab4718d6d2915
- git.kernel.org /stable/c/ab9ed9faa67bf67383ff7e1479655e232a843c2b
- git.kernel.org /stable/c/3b0f604df9e2b9a456f1ae5266a439998c4c8826
- git.kernel.org /stable/c/3f968dcdf018861129f97910fa7bd680d939a9b0
- git.kernel.org /stable/c/985a568171e7bdba6dcde3420d0e5bb515813457
- git.kernel.org /stable/c/6745fa65f4115045431c0c15610e876855a04625
- git.kernel.org /stable/c/526fac219e8b7d3369b43026bd0a1df51b811cd4
- git.kernel.org /stable/c/7a39c732a22ec4a369af9e19fbe3d666ec83eec4
Sources
- CVE List CVE-2026-98856
- NVD CVE-2026-98856
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.