CVE-2026-98902: Linux kernel · md/raid5: let stripe batch bm_seq comparison wrap-safe
Source GCVE Database
Not known to be exploited · fixed in ffdd3aee932fc293456678f6b0200ffe9bf12a6d : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ffdd3aee932fc293456678f6b0200ffe9bf12a6d, cc8eb1715673de850f14376782151f68f73ae3ce, c5c89e1a872a84019f674f5107111e6e6b7cc30f +4
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix has been applied in the Linux kernel to address this issue by making the bm_seq comparison wrap-safe. Users should update to the fixed kernel version once available. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for current remediation guidance.
Description
A vulnerability in the Linux kernel's md/raid5 component related to the handling of 32-bit sequence numbers (bm_seq) has been resolved. The issue involved incorrect comparison logic when the 32-bit sequence number wraps around, causing newer sequence numbers to appear smaller than older ones. This was addressed by implementing a wrap-safe comparison method.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98902 (opens in a new tab)
- git.kernel.org/stable/c/00e93faf4cea9e8802ac5dfee0952d84fc95c40f (opens in a new tab)
- git.kernel.org/stable/c/2fdc51228d9a8cad2d727d5aef732cc66fc6d56e (opens in a new tab)
- git.kernel.org/stable/c/628b14d0744bd5dfe176ea93559071cdcde14255 (opens in a new tab)
- git.kernel.org/stable/c/647c7289a3960118e249c0a53da6f1ebba1e47a3 (opens in a new tab)
- git.kernel.org/stable/c/c5c89e1a872a84019f674f5107111e6e6b7cc30f (opens in a new tab)
- git.kernel.org/stable/c/cc8eb1715673de850f14376782151f68f73ae3ce (opens in a new tab)
- git.kernel.org/stable/c/ffdd3aee932fc293456678f6b0200ffe9bf12a6d (opens in a new tab)