CVE-2026-98902 json
md/raid5: let stripe batch bm_seq comparison wrap-safe
published 19d ago modified 17d ago also EUVD-2026-108858
- 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 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
md/raid5: let stripe batch bm_seq comparison wrap-safe
Once the 32-bit seq wraps, a newer bm_seq can look smaller than old, so .. covert to wrap-safe calculate way.
Patch / fix
- Linux Linux 7.2
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.6-1
debian advisories DEBIAN-CVE-2026-98902
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98902
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.159.1-1
azure linux advisories AZL-110662
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/647c7289a3960118e249c0a53da6f1ebba1e47a3 commit
- git.kernel.org/stable/c/ffdd3aee932fc293456678f6b0200ffe9bf12a6d commit
- git.kernel.org/stable/c/628b14d0744bd5dfe176ea93559071cdcde14255 commit
- git.kernel.org/stable/c/2fdc51228d9a8cad2d727d5aef732cc66fc6d56e commit
- git.kernel.org/stable/c/c5c89e1a872a84019f674f5107111e6e6b7cc30f commit
- git.kernel.org/stable/c/cc8eb1715673de850f14376782151f68f73ae3ce commit
- git.kernel.org/stable/c/00e93faf4cea9e8802ac5dfee0952d84fc95c40f commit
Is CVE-2026-98902 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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-98902 updated cvss 4.7
kernel: md/raid5: let stripe batch bm_seq comparison wrap-safe
-
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.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/647c7289a3960118e249c0a53da6f1ebba1e47a3
- git.kernel.org /stable/c/ffdd3aee932fc293456678f6b0200ffe9bf12a6d
- git.kernel.org /stable/c/628b14d0744bd5dfe176ea93559071cdcde14255
- git.kernel.org /stable/c/2fdc51228d9a8cad2d727d5aef732cc66fc6d56e
- git.kernel.org /stable/c/c5c89e1a872a84019f674f5107111e6e6b7cc30f
- git.kernel.org /stable/c/cc8eb1715673de850f14376782151f68f73ae3ce
- git.kernel.org /stable/c/00e93faf4cea9e8802ac5dfee0952d84fc95c40f
Sources
- CVE List CVE-2026-98902
- NVD CVE-2026-98902
Fencer Intel 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.