CVE-2025-21712

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

MEDIUM
5.5
CVSS Score
Published: February 27, 2025 at 02:07 AM UTC
Updated: October 15, 2026 at 10:18 PM UTC
4 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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: <TASK> 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.13 ≤ v < 6.1.1306.13 ≤ v < 6.13.26.2 ≤ v < 6.6.806.7 ≤ v < 6.12.132.6.1332a7627cf3a35396a8e834faf34e38ae9f3b1309
Vendor states this is fixed in 032fa54f486eac5507976e7e31f079a767bc13a8 (fixed)
Vendor states this is fixed in 237e19519c8ff6949f0ef57c4a0243f5b2b0fa18 (fixed)
Vendor states this is fixed in 4e9316eee3885bfb311b4759513f2ccf37891c09 (fixed)
Vendor states this is fixed in 52848a095b55a302af92f52ca0de5b3112059bb8 (fixed)
Vendor states this is fixed in 8d28d0ddb986f56920ac97ae704cc3340a699a30 (fixed)
Vendor states this is fixed in eb2f9d98cd3e94a79fbf8fb90637c5b12e805428 (fixed)
Vendor states this is fixed in 2.6.13 (unaffected)
Vendor states this is fixed in 5.15.209 (unaffected)
Vendor states this is fixed in 6.1.130 (unaffected)
Vendor states this is fixed in 6.12.13 (unaffected)
Vendor states this is fixed in 6.13.2 (unaffected)
Vendor states this is fixed in 6.14 (unaffected)
Vendor states this is fixed in 6.6.80 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card