CVE-2025-22124

Source
https://nvd.nist.gov/vuln/detail/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
Related
Published
2025-04-16T15:16:06Z
Modified
2025-07-29T11:19:24.481496Z
Summary
[none]
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, pgindex in _writesbpage() could equal to bitmap->storage.filepages. Then bitmaplimit will be calculated to 0. mdsuperwrite() will be called with 0 size. That means the first 4k sb area of node 1 will never be updated through filemapwritepage(). This bug causes hang of mdadm/clustermdtests/01r1Grow_resize.

Here use (pgindex % bitmap->storage.filepages) to make calculation of bitmap_limit correct.

References

Affected packages

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

6.*

6.12.38-1
6.13~rc6-1~exp1
6.13~rc7-1~exp1
6.13.2-1~exp1
6.13.3-1~exp1
6.13.4-1~exp1
6.13.5-1~exp1
6.13.6-1~exp1
6.13.7-1~exp1
6.13.8-1~exp1
6.13.9-1~exp1
6.13.10-1~exp1
6.13.11-1~exp1
6.14.3-1~exp1
6.14.5-1~exp1
6.14.6-1~exp1
6.15~rc7-1~exp1
6.15-1~exp1
6.15.1-1~exp1
6.15.2-1~exp1
6.15.3-1~exp1
6.15.4-1~exp1
6.15.5-1~exp1
6.15.6-1~exp1
6.16~rc7-1~exp1

Ecosystem specific

{
    "urgency": "not yet assigned"
}