CVE-2025-38141: dm: fix dm_blk_report_zones
Noroxi assessment
Priority: Monitor (action score 31/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.19% (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 37f53a2c60d03743e0eacf7a0c01c279776fef4e, d19bc1b4dd5f322980b1f05f79b2ea4f0db10920, f9c1bdf24615303d48a2d0fd629c88f3189563aa.
Low priority for now. Upgrade to Linux Linux 37f53a2c60d03743e0eacf7a0c01c279776fef4e, d19bc1b4dd5f322980b1f05f79b2ea4f0db10920, f9c1bdf24615303d48a2d0fd629c88f3189563aa 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: dm: fix dm_blk_report_zones If dm_get_live_table() returned NULL, dm_put_live_table() was never called. Also, it is possible that md->zone_revalidate_map will change while calling this function. Only read it once, so that we are always using the same value. Otherwise we might miss a call to dm_put_live_table(). Finally, while md->zone_revalidate_map is set and a process is calling blk_revalidate_disk_zones() to set up the zone append emulation resources, it is possible that another process, perhaps triggered by blkdev_report_zones_ioctl(), will call dm_blk_report_zones(). If blk_revalidate_disk_zones() fails, these resources can be freed while the other process is still using them, causing a use-after-free error. blk_revalidate_disk_zones() will only ever be called when initially setting up the zone append emulation resources, such as when setting up a zoned dm-crypt table for the first time. Further table swaps will not set md->zone_revalidate_map or call blk_revalidate_disk_zones(). However it must be called using the new table (referenced by md->zone_revalidate_map) and the new queue limits while the DM device is suspended. dm_blk_report_zones() needs some way to distinguish between a call from blk_revalidate_disk_zones(), which must be allowed to use md->zone_revalidate_map to access this not yet activated table, and all other calls to dm_blk_report_zones(), which should not be allowed while the device is suspended and cannot use md->zone_revalidate_map, since the zone resources might be freed by the process currently calling blk_revalidate_disk_zones(). Solve this by tracking the process that sets md->zone_revalidate_map in dm_revalidate_zones() and only allowing that process to make use of it in dm_blk_report_zones().
- Published
- Jul 3, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.10 and later · before 6.12.34
- linux linux kernel6.13 and later · before 6.15.3
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
- 6.10affected
- f211268ed1f9bdf48f06a3ead5f5d88437450579 and later · before f9c1bdf24615303d48a2d0fd629c88f3189563aaaffected · git
- f211268ed1f9bdf48f06a3ead5f5d88437450579 and later · before d19bc1b4dd5f322980b1f05f79b2ea4f0db10920affected · git
- f211268ed1f9bdf48f06a3ead5f5d88437450579 and later · before 37f53a2c60d03743e0eacf7a0c01c279776fef4eaffected · git
- before 6.10not affected · semver
- 6.12.34 and later · up to and including 6.12.*not affected · semver
- 6.15.3 and later · up to and including 6.15.*not affected · semver
- 6.16 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-124.43.1.el10_1 | 6.12.0-124.43.1.el10_1 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-124.43.1.el10_1 | 6.12.0-124.43.1.el10_1 |
| AlmaLinux:9 | kernel | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-core | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-611.26.1.el9_7 | 5.14.0-611.26.1.el9_7 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38138Jul 3, 2025 · dmaengine: ti: Add NULL check in udma_probe()22Monitor
- ← EarlierCVE-2025-38139Jul 3, 2025 · netfs: Fix oops in write-retry from mis-resetting the subreq iterator28Monitor
- Later →CVE-2025-38142Jul 3, 2025 · hwmon: (asus-ec-sensors) check sensor index in read_string()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 37f53a2c60d03743e0eacf7a0c01c279776fef4e | Vendor (CNA) |
| Linux Linux | d19bc1b4dd5f322980b1f05f79b2ea4f0db10920 | Vendor (CNA) |
| Linux Linux | f9c1bdf24615303d48a2d0fd629c88f3189563aa | Vendor (CNA) |
| almalinux:kernel | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-611.26.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.12.35-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:kernel | 0:5.14.0-611.26.1.el9_7 · Rocky Linux:9 | Package 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.