VDB

CVE-2025-38141

CVE-2025-38141 PUBLISHED CVSS 7.8 HIGH

dm: fix dm_blk_report_zones

Reported by linux · Published July 3, 2025

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().

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinuxf9c1bdf24615303d48a2d0fd629c88f3189563aa, d19bc1b4dd5f322980b1f05f79b2ea4f0db10920, 6.10, 37f53a2c60d03743e0eacf7a0c01c279776fef4e

Risk scores

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

Affected products

VendorProductVersions
LinuxLinuxf211268ed1f9bdf48f06a3ead5f5d88437450579, f211268ed1f9bdf48f06a3ead5f5d88437450579, f211268ed1f9bdf48f06a3ead5f5d88437450579
LinuxLinux6.10, 0, 6.12.34
LinuxLinux6.10, *, *
amazon:2023kernel-libbpf-static0
amazon:2023kernel6.120
amazon:2023kernel6.12-modules-extra0
amazon:2023kernel-headers0
amazon:2023bpftool0
linuxlinux_kernel6.10, 6.10, 6.10
amazon:2023python3-perf6.120
amazon:2023kernel-devel0
amazon:2023kernel-libbpf0
amazon:2023kernel-tools-devel0
amazon:2023kernel-tools0
amazon:2023kernel-modules-extra-common0
amazon:2023perf6.120
amazon:2023kernel-livepatch-6.12.35-55.1030
amazon:2023kernel-libbpf-devel0

Timeline

  • Jul 2, 2025 CVE Published
  • Jul 3, 2025 EPSS Score (30 in total, the first dated here)
  • Oct 12, 2025 PoC Published (10 in total, the first dated here)
  • Mar 31, 2026 Distribution Patch (191 in total, the first dated here)
  • Mar 31, 2026 Security Advisory (205 in total, the first dated here)
  • Jun 9, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-38141
vulnetix vdb fixes CVE-2025-38141

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38141/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›