CVE-2025-22124
- Source
- https://cve.org/CVERecord?id=CVE-2025-22124
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-22124.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2025-22124
- Downstream
AZL (1)
BELL (1)
DEBIAN (1)
MINI (1)
ROOT (3)
SUSE (11)
- Related
- Published
- 2025-04-16T14:13:08Z
- Modified
- 2026-10-20T10:30:31Z
- Severity
-
- 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb
- Details
-
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.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/22xxx/CVE-2025-22124.json" }- References
-
- https://git.kernel.org/stable/c/5eaf57fdfa37c869e61e9908e03edd707f9145b8
- https://git.kernel.org/stable/c/60196f92bbc7901eb5cfa5d456651b87ea50a4a3
- https://git.kernel.org/stable/c/6130825f34d41718c98a9b1504a79a23e379701e
- https://git.kernel.org/stable/c/bc3a9788961631359527763d7e1fcf26554c7cb1
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/22xxx/CVE-2025-22124.json
- https://nvd.nist.gov/vuln/detail/CVE-2025-22124
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced655cc01889fa9b65441922565cddee64af49e6d6Fixed5eaf57fdfa37c869e61e9908e03edd707f9145b8
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedab99a87542f194f28e2364a42afbf9fb48b1c724Fixed60196f92bbc7901eb5cfa5d456651b87ea50a4a3Fixedbc3a9788961631359527763d7e1fcf26554c7cb1Fixed6130825f34d41718c98a9b1504a79a23e379701e
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6.6.44Fixed6.6.157
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6.10.3Fixed6.11
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced5600d6013c634c2b6b6c6c55c8ecb50c3a6211f2