CVE-2025-21712

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-02-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

md/md-bitmap: Synchronize bitmap_get_stats() with bitmap lifetime

After commit ec6bb299c7c3 ("md/md-bitmap: add 'sync_size' into struct md_bitmap_stats"), following panic is reported:

Oops: general protection fault, probably for non-canonical address RIP: 0010:bitmap_get_stats+0x2b/0xa0 Call Trace: md_seq_show+0x2d2/0x5b0 seq_read_iter+0x2b9/0x470 seq_read+0x12f/0x180 proc_reg_read+0x57/0xb0 vfs_read+0xf6/0x380 ksys_read+0x6c/0xf0 do_syscall_64+0x82/0x170 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Root cause is that bitmap_get_stats() can be called at anytime if mddev is still there, even if bitmap is destroyed, or not fully initialized. Deferenceing bitmap in this case can crash the kernel. Meanwhile, the above commit start to deferencing bitmap->storage, make the problem easier to trigger.

Fix the problem by protecting bitmap_get_stats() with bitmap_info.mutex.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

February 27, 2025

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Aug 2, 2026
⚠️ Active exploitation confirmed. Patch available.
generic Patch Available

[SECURITY] [DLA 4193-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html
generic

md/md-bitmap: Synchronize bitmap_get_stats() with bitmap lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eb2f9d98cd3e94a79fbf8fb90637c5b12e805428
generic

md/md-bitmap: Synchronize bitmap_get_stats() with bitmap lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d28d0ddb986f56920ac97ae704cc3340a699a30
generic

md/md-bitmap: Synchronize bitmap_get_stats() with bitmap lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52848a095b55a302af92f52ca0de5b3112059bb8
generic

md/md-bitmap: Synchronize bitmap_get_stats() with bitmap lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e9316eee3885bfb311b4759513f2ccf37891c09
generic

md/md-bitmap: Synchronize bitmap_get_stats() with bitmap lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/237e19519c8ff6949f0ef57c4a0243f5b2b0fa18
generic

md/md-bitmap: Synchronize bitmap_get_stats() with bitmap lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/032fa54f486eac5507976e7e31f079a767bc13a8

Vendor Advisories for CVE-2025-21712(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(19)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(20)

Data Freshness Timeline

(refreshed 10× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 151 total refreshes for this CVE.

  1. 2026-08-07 16:26 UTCEPSS rescore
  2. 2026-08-06 13:46 UTCEPSS rescore
  3. 2026-08-05 19:16 UTCEPSS rescore
  4. 2026-08-05 14:04 UTCEG score recompute
  5. 2026-08-05 14:04 UTCVendor advisory
  6. 2026-08-05 14:04 UTCGHSA enrichment
  7. 2026-08-04 15:09 UTCEPSS rescore
  8. 2026-08-04 10:37 UTCEPSS rescore
  9. 2026-08-03 10:35 UTCEPSS rescore
  10. 2026-08-02 02:25 UTCEPSS rescore
  11. 2026-08-01 04:15 UTCEPSS rescore
  12. 2026-07-30 16:27 UTCEPSS rescore
  13. 2026-07-30 07:23 UTCEG score recompute
  14. 2026-07-30 07:23 UTCVendor advisory
  15. 2026-07-30 07:23 UTCGHSA enrichment
  16. 2026-07-30 06:24 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  17. 2026-07-30 01:29 UTCEPSS rescore
  18. 2026-07-28 15:35 UTCEPSS rescore
  19. 2026-07-28 01:25 UTCOSV refresh
  20. 2026-07-27 14:12 UTCEPSS rescore
  21. 2026-07-26 14:53 UTCEPSS rescore
  22. 2026-07-25 14:17 UTCEPSS rescore
  23. 2026-07-23 14:17 UTCEPSS rescore
  24. 2026-07-23 02:50 UTCEG score recompute
  25. 2026-07-22 14:07 UTCEPSS rescore
Show 75 more
  1. 2026-07-22 14:07 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:07 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:03 UTCEPSS rescore
  9. 2026-07-16 17:02 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 01:59 UTCEPSS rescore
  13. 2026-07-14 13:11 UTCMITRE cvelistV5
  14. 2026-07-13 22:29 UTCEPSS rescore
  15. 2026-07-13 22:29 UTCEPSS rescore
  16. 2026-07-13 06:12 UTCEPSS rescore
  17. 2026-07-13 06:12 UTCEPSS rescore
  18. 2026-07-12 05:46 UTCEPSS rescore
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-11 08:26 UTCEPSS rescore
  22. 2026-07-10 17:52 UTCOSV refresh
  23. 2026-07-09 19:09 UTCEPSS rescore
  24. 2026-07-08 15:14 UTCEPSS rescore
  25. 2026-07-07 13:45 UTCEPSS rescore
  26. 2026-07-06 16:26 UTCEPSS rescore
  27. 2026-07-06 02:22 UTCEPSS rescore
  28. 2026-07-06 02:22 UTCEPSS rescore
  29. 2026-07-05 02:30 UTCEPSS rescore
  30. 2026-07-04 06:30 UTCEPSS rescore
  31. 2026-07-01 15:06 UTCEPSS rescore
  32. 2026-06-30 23:21 UTCEPSS rescore
  33. 2026-06-30 23:21 UTCEPSS rescore
  34. 2026-06-29 14:06 UTCEPSS rescore
  35. 2026-06-28 14:07 UTCEPSS rescore
  36. 2026-06-28 14:07 UTCEPSS rescore
  37. 2026-06-28 04:55 UTCEPSS rescore
  38. 2026-06-28 04:55 UTCEPSS rescore
  39. 2026-06-27 03:08 UTCEPSS rescore
  40. 2026-06-27 03:08 UTCEPSS rescore
  41. 2026-06-25 13:49 UTCEPSS rescore
  42. 2026-06-25 13:49 UTCEPSS rescore
  43. 2026-06-24 14:04 UTCEPSS rescore
  44. 2026-06-24 14:04 UTCEPSS rescore
  45. 2026-06-23 21:32 UTCEPSS rescore
  46. 2026-06-23 21:32 UTCEPSS rescore
  47. 2026-06-22 14:25 UTCEPSS rescore
  48. 2026-06-22 14:25 UTCEPSS rescore
  49. 2026-06-22 02:07 UTCOSV refresh
  50. 2026-06-21 14:56 UTCEPSS rescore
  51. 2026-06-21 14:56 UTCEPSS rescore
  52. 2026-06-21 01:59 UTCEPSS rescore
  53. 2026-06-21 01:59 UTCEPSS rescore
  54. 2026-06-19 19:25 UTCEPSS rescore
  55. 2026-06-19 19:25 UTCEPSS rescore
  56. 2026-06-18 17:52 UTCEPSS rescore
  57. 2026-06-18 17:52 UTCEPSS rescore
  58. 2026-06-17 17:52 UTCEPSS rescore
  59. 2026-06-16 17:52 UTCEPSS rescore
  60. 2026-06-16 17:52 UTCEPSS rescore
  61. 2026-06-15 17:48 UTCEPSS rescore
  62. 2026-06-14 23:17 UTCEPSS rescore
  63. 2026-06-13 22:59 UTCEPSS rescore
  64. 2026-06-12 23:11 UTCEPSS rescore
  65. 2026-06-11 13:59 UTCEPSS rescore
  66. 2026-06-10 22:18 UTCEPSS rescore
  67. 2026-06-10 13:22 UTCEPSS rescore
  68. 2026-06-08 14:16 UTCEPSS rescore
  69. 2026-06-08 14:16 UTCEPSS rescore
  70. 2026-06-07 15:24 UTCEPSS rescore
  71. 2026-06-07 15:24 UTCEPSS rescore
  72. 2026-06-06 13:47 UTCEPSS rescore
  73. 2026-06-06 13:47 UTCEPSS rescore
  74. 2026-06-05 22:46 UTCEPSS rescore
  75. 2026-06-05 22:46 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-21712?
CVE-2025-21712 is a medium vulnerability published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: md/md-bitmap: Synchronize bitmapgetstats() with bitmap lifetime After commit ec6bb299c7c3 ("md/md-bitmap: add 'sync_size' into struct mdbitmapstats"), following panic is reported: Oops: general protection fault, probably for…
When was CVE-2025-21712 disclosed?
CVE-2025-21712 was first published in the National Vulnerability Database on February 27, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-21712 actively exploited?
CVE-2025-21712 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.8% of all scored CVEs.
What is the CVSS score of CVE-2025-21712?
CVE-2025-21712 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21712?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-21712, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-21712

Explore →

Is Your Infrastructure Affected by CVE-2025-21712?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.