Answer in brief
CVE-2025-22124 records a High severity (CVSS 7.8) vulnerability in md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ab99a87542f194f28e2364a42afbf9fb48b1c724 <60196f92bbc7901eb5cfa5d456651b87ea50a4a3 || >=ab99a87542f194f28e2364a42afbf9fb48b1c724 <bc3a9788961631359527763d7e1fcf26554c7cb1 || >=ab99a87542f194f28e2364a42afbf9fb48b1c724 <6130825f34d41718c98a9b1504a79a23e379701e || 655cc01889fa9b65441922565cddee64af49e6d6 || 5600d6013c634c2b6b6c6c55c8ecb50c3a6211f2 || >=6.6.44 <6.7 || >=6.10.3 <6.11 | 60196f92bbc7901eb5cfa5d456651b87ea50a4a3, bc3a9788961631359527763d7e1fcf26554c7cb1, 6130825f34d41718c98a9b1504a79a23e379701e, 6.7, 6.11 |
| Linux/Linuxgeneric | 6.11 | Not reported |
| Linux/Linuxgeneric | >=655cc01889fa9b65441922565cddee64af49e6d6 <5eaf57fdfa37c869e61e9908e03edd707f9145b8 || >=ab99a87542f194f28e2364a42afbf9fb48b1c724 <60196f92bbc7901eb5cfa5d456651b87ea50a4a3 || >=ab99a87542f194f28e2364a42afbf9fb48b1c724 <bc3a9788961631359527763d7e1fcf26554c7cb1 || >=ab99a87542f194f28e2364a42afbf9fb48b1c724 <6130825f34d41718c98a9b1504a79a23e379701e || 5600d6013c634c2b6b6c6c55c8ecb50c3a6211f2 || >=6.6.44 <6.6.157 || >=6.10.3 <6.11 | 5eaf57fdfa37c869e61e9908e03edd707f9145b8, 60196f92bbc7901eb5cfa5d456651b87ea50a4a3, bc3a9788961631359527763d7e1fcf26554c7cb1, 6130825f34d41718c98a9b1504a79a23e379701e, 6.6.157, 6.11 |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.