CVE-2025-22124md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb
- 7.8HighCVSS base score
- 0.20%Exploitation in 30 daysEPSS · top 90% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 4 months later
· 4 months later
Published
- 18 months later
· 18 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 655cc01889fa9b65441922565cddee64af49e6d6 – < 5eaf57fdfa37c869e61e9908e03edd707f9145b8
- affected ab99a87542f194f28e2364a42afbf9fb48b1c724 – < 60196f92bbc7901eb5cfa5d456651b87ea50a4a3
- affected ab99a87542f194f28e2364a42afbf9fb48b1c724 – < bc3a9788961631359527763d7e1fcf26554c7cb1
- affected ab99a87542f194f28e2364a42afbf9fb48b1c724 – < 6130825f34d41718c98a9b1504a79a23e379701e
- affected 5600d6013c634c2b6b6c6c55c8ecb50c3a6211f2
- affected 6.6.44 – < 6.6.157
- affected 6.10.3 – < 6.11
- affected 6.11
- unaffected < 6.11
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.46 – ≤ 6.12.*
- unaffected 6.14.2 – ≤ 6.14.*
- unaffected 6.15 – ≤ *
References
References4
- https://git.kernel.org/stable/c/5eaf57fdfa37c869e61e9908e03edd707f9145b8 (opens in a new tab)
- https://git.kernel.org/stable/c/60196f92bbc7901eb5cfa5d456651b87ea50a4a3 (opens in a new tab)
- https://git.kernel.org/stable/c/bc3a9788961631359527763d7e1fcf26554c7cb1 (opens in a new tab)
- https://git.kernel.org/stable/c/6130825f34d41718c98a9b1504a79a23e379701e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-11191 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-22124)Record last updated .