CVE-2025-22124

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. CVE-2025-22124
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.

5.5 /10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://git.kernel.org/stable/c/60196f92bbc7901eb5cfa5d456651b87ea50a4a3 Patch
https://git.kernel.org/stable/c/6130825f34d41718c98a9b1504a79a23e379701e Patch
https://git.kernel.org/stable/c/bc3a9788961631359527763d7e1fcf26554c7cb1 Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
History

03 Nov 2025, 18:27

Type Values Removed Values Added
First Time Linux
Linux linux Kernel
CWE NVD-CWE-noinfo
References () https://git.kernel.org/stable/c/60196f92bbc7901eb5cfa5d456651b87ea50a4a3 - () https://git.kernel.org/stable/c/60196f92bbc7901eb5cfa5d456651b87ea50a4a3 - Patch
References () https://git.kernel.org/stable/c/6130825f34d41718c98a9b1504a79a23e379701e - () https://git.kernel.org/stable/c/6130825f34d41718c98a9b1504a79a23e379701e - Patch
References () https://git.kernel.org/stable/c/bc3a9788961631359527763d7e1fcf26554c7cb1 - () https://git.kernel.org/stable/c/bc3a9788961631359527763d7e1fcf26554c7cb1 - Patch
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 5.5

09 Sep 2025, 17:15

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: md/md-bitmap: corrige bitmap_limit incorrecto para clustermd al escribir sb En clustermd, se usan mapas de bits de intención de escritura separados para cada nodo del clúster: 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] | | | Entonces, en el nodo 1, pg_index en __write_sb_page() podría ser igual a bitmap->storage.file_pages. Entonces, bitmap_limit se calculará como 0. md_super_write() se llamará con un tamaño de 0. Esto significa que la primera área de 4k del nodo 1 nunca se actualizará mediante filemap_write_page(). Este error provoca el bloqueo de mdadm/clustermd_tests/01r1_Grow_resize. En este caso, utilice (pg_index % bitmap->storage.file_pages) para que el cálculo de bitmap_limit sea correcto.
References
  • () https://git.kernel.org/stable/c/60196f92bbc7901eb5cfa5d456651b87ea50a4a3 -

16 Apr 2025, 15:16

Type Values Removed Values Added
New CVE
Information

Published : 2025-04-16 15:16

Updated : 2025-11-03 18:27

NVD link : CVE-2025-22124

Mitre link : CVE-2025-22124

CVE.ORG link : CVE-2025-22124

JSON object : View

Products Affected

linux

  • linux_kernel
CWE
NVD-CWE-noinfo