CVE Catalog

CVE-2025-22124

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.19%

8th percentile - higher than 8% of all known CVEs

Summary

In the Linux kernel, the md/md-bitmap driver has a bug causing incorrect bitmap_limit calculation in clustered mode (clustermd). As a result, the bitmap superblock area for a cluster node was not updated, leading to hangs in mdadm during resize tests.

Risk Assessment

The organization may experience crashes or hangs of RAID systems managed by mdadm in clustered configurations, potentially leading to data unavailability and service disruption.

Recommendation

Immediately update the Linux kernel to a version containing the fix for CVE-2025-22124, especially in clustered environments using md/md-bitmap.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb In clustermd, separate write-intent-bitmaps are used for each cluster node: 0 4k 8k 12k ------------------------------------------------------------------- | idle | md super | bm super [0] + bits | | bm bits[0, contd] | bm super[1] + bits | bm bits[1, contd] | | bm super[2] + bits | bm bits [2, contd] | bm super[3] + bits | | bm bits [3, contd] | | | So in node 1, pg_index in __write_sb_page() could equal to bitmap->storage.file_pages. Then bitmap_limit will be calculated to 0. md_super_write() will be called with 0 size. That means the first 4k sb area of node 1 will never be updated through filemap_write_page(). This bug causes hang of mdadm/clustermd_tests/01r1_Grow_resize. Here use (pg_index % bitmap->storage.file_pages) to make calculation of bitmap_limit correct.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS