Cloudanix VulnDB

CVE-2026-98902

None

CVSS

—

EPSS

0.2%

Published

Oct 23, 2026

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A storage handling error on Linux servers could silently corrupt data or slow down disk arrays after long periods of heavy use.

Exploitation
Local Privilege
Attacker needs
Local User
Complexity
Moderate
Impact
Data Tampering
Component
OS kernel
Class
Race Condition
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Incorrect 32-bit sequence number comparison in md/raid5 stripe batching fails to handle wrap-around, allowing a newer bm_seq to be treated as older and producing wrong batch decisions under concurrent access.

Why it matters to the business

Linux systems using software RAID5 arrays may experience data corruption, I/O errors, or degraded performance after prolonged operation when sequence counters overflow, increasing unplanned downtime and recovery costs.

How an attack unfolds

An attacker with local access triggers high-volume concurrent I/O against a RAID5 volume to force rapid bm_seq increments until wrap-around occurs, then races operations so the kernel misorders stripe batches and produces inconsistent parity or data writes.

How to fix it

Upgrade the Linux kernel to a version containing the wrap-safe bm_seq comparison fix for md/raid5; rebuild and reboot into the patched kernel; verify RAID arrays remain consistent after upgrade.

How to confirm the fix worked

Confirm the running kernel contains the upstream md/raid5 wrap-safe patch; inspect /proc/mdstat and dmesg for absence of stripe batch anomalies; run fsck or RAID consistency checks on affected arrays.

Typical attack path

  1. Obtain local unprivileged access on a Linux host with md RAID5 arrays
  2. Generate sustained parallel write workloads to accelerate 32-bit bm_seq rollover
  3. Time additional I/O operations to exploit the non-wrap-safe comparison window
  4. Trigger kernel decisions that treat newer sequences as older, corrupting stripe state

How to detect it

Review kernel logs for md/raid5 stripe batch warnings or parity mismatches; correlate with high I/O workloads that could trigger sequence rollover; examine audit logs for unusual local process activity on RAID hosts.

What your security team should do

  • Prioritize kernel updates on all systems exposing md RAID5 volumes
  • Monitor EPSS and KEV updates for any rise in exploit maturity
  • Add kernel version checks to vulnerability scanning policies

The record

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.

Affected packages

Ecosystem Package Introduced Fixed