Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-21712: md/md-bitmap: Synchronize bitmap_get_stats() with bitmap lifetime

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 032fa54f486eac5507976e7e31f079a767bc13a8, 237e19519c8ff6949f0ef57c4a0243f5b2b0fa18, 4e9316eee3885bfb311b4759513f2ccf37891c09.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 032fa54f486eac5507976e7e31f079a767bc13a8, 237e19519c8ff6949f0ef57c4a0243f5b2b0fa18, 4e9316eee3885bfb311b4759513f2ccf37891c09 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Feb 27, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-21712

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.13affected
    • 32a7627cf3a35396a8e834faf34e38ae9f3b1309 and later · before eb2f9d98cd3e94a79fbf8fb90637c5b12e805428affected · git
    • 32a7627cf3a35396a8e834faf34e38ae9f3b1309 and later · before 032fa54f486eac5507976e7e31f079a767bc13a8affected · git
    • 32a7627cf3a35396a8e834faf34e38ae9f3b1309 and later · before 52848a095b55a302af92f52ca0de5b3112059bb8affected · git
    • 32a7627cf3a35396a8e834faf34e38ae9f3b1309 and later · before 237e19519c8ff6949f0ef57c4a0243f5b2b0fa18affected · git
    • 32a7627cf3a35396a8e834faf34e38ae9f3b1309 and later · before 4e9316eee3885bfb311b4759513f2ccf37891c09affected · git
    • 32a7627cf3a35396a8e834faf34e38ae9f3b1309 and later · before 8d28d0ddb986f56920ac97ae704cc3340a699a30affected · git
    • before 2.6.13not affected · semver
    • 5.15.209 and later · up to and including 5.15.*not affected · semver
    • 6.1.130 and later · up to and including 6.1.*not affected · semver
Affected versions · NVD (4)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.13 and later · before 6.1.130
  • linux linux kernel6.2 and later · before 6.6.80
  • linux linux kernel6.7 and later · before 6.12.13
  • linux linux kernel6.13 and later · before 6.13.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.133-16.1.133-1
Debian:13linuxbefore 6.12.13-16.12.13-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-21708Feb 27, 2025 · net: usb: rtl8150: enable basic endpoint checking
    22Monitor
  • ← EarlierCVE-2025-21709Feb 27, 2025 · kernel: be more careful about dup_mmap() failures and uprobe registering
    22Monitor
  • Later →CVE-2025-21714Feb 27, 2025 · RDMA/mlx5: Fix implicit ODP use after free
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux032fa54f486eac5507976e7e31f079a767bc13a8Vendor (CNA)
Linux Linux237e19519c8ff6949f0ef57c4a0243f5b2b0fa18Vendor (CNA)
Linux Linux4e9316eee3885bfb311b4759513f2ccf37891c09Vendor (CNA)
Linux Linux52848a095b55a302af92f52ca0de5b3112059bb8Vendor (CNA)
Linux Linux8d28d0ddb986f56920ac97ae704cc3340a699a30Vendor (CNA)
Linux Linuxeb2f9d98cd3e94a79fbf8fb90637c5b12e805428Vendor (CNA)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0—Microsoft (MSRC)
debian:linux6.1.133-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records