CVE-2026-98902: Linux kernel · md/raid5: let stripe batch bm_seq comparison wrap-safe
Affects Linux kernelSource CVE Database V5
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 is available and has been applied in multiple Linux kernel commits. Users should update to a Linux kernel version that includes these fixes to mitigate the vulnerability.
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 the comparison of stripe batch sequence numbers that could wrap around, causing newer sequence numbers to appear smaller than older ones. This was fixed by implementing a wrap-safe calculation method for bm_seq comparisons.
References
- git.kernel.org/stable/c/647c7289a3960118e249c0a53da6f1ebba1e47a3 (opens in a new tab)
- git.kernel.org/stable/c/ffdd3aee932fc293456678f6b0200ffe9bf12a6d (opens in a new tab)
- git.kernel.org/stable/c/628b14d0744bd5dfe176ea93559071cdcde14255 (opens in a new tab)
- git.kernel.org/stable/c/2fdc51228d9a8cad2d727d5aef732cc66fc6d56e (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/00e93faf4cea9e8802ac5dfee0952d84fc95c40f (opens in a new tab)