CVE-2025-38451: md/md-bitmap: fix GPF in bitmap_get_stats()
In the Linux kernel, the following vulnerability has been resolved:
md/md-bitmap: fix GPF in bitmapgetstats()
The commit message of commit 6ec1f0239485 ("md/md-bitmap: fix stats collection for external bitmaps") states:
Remove the external bitmap check as the statistics should be available regardless of bitmap storage location.
Return -EINVAL only for invalid bitmap with no storage (neither in superblock nor in external file).
But, the code does not adhere to the above, as it does only check for a valid super-block for "internal" bitmaps. Hence, we observe:
Oops: GPF, probably for non-canonical address 0x1cd66f1f40000028 RIP: 0010:bitmapgetstats+0x45/0xd0 Call Trace:
seqreaditer+0x2b9/0x46a seqread+0x12f/0x180 procregread+0x57/0xb0 vfsread+0xf6/0x380 ksysread+0x6d/0xf0 dosyscall64+0x8c/0x1b0 entrySYSCALL64afterhwframe+0x76/0x7e
We fix this by checking the existence of a super-block for both the internal and external case.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch 6ec1f0239485
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38451?
CVE-2025-38451 has been rated as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2025-38451?
To fix CVE-2025-38451, update your Linux kernel to the latest stable version that includes the patch.
What are the risks associated with CVE-2025-38451?
The risks associated with CVE-2025-38451 include potential system instability and unexpected behavior in systems that rely on bitmap statistics.
Which versions of the Linux kernel are affected by CVE-2025-38451?
CVE-2025-38451 affects various versions of the Linux kernel prior to the fix incorporated in stable releases after the identified commit.
Is CVE-2025-38451 being actively exploited?
As of now, there is no known active exploitation of CVE-2025-38451 in the wild.