{"id":"CVE-2025-38141","state":"PUBLISHED","title":"dm: fix dm_blk_report_zones","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndm: fix dm_blk_report_zones\n\nIf dm_get_live_table() returned NULL, dm_put_live_table() was never\ncalled. Also, it is possible that md->zone_revalidate_map will change\nwhile calling this function. Only read it once, so that we are always\nusing the same value. Otherwise we might miss a call to\ndm_put_live_table().\n\nFinally, while md->zone_revalidate_map is set and a process is calling\nblk_revalidate_disk_zones() to set up the zone append emulation\nresources, it is possible that another process, perhaps triggered by\nblkdev_report_zones_ioctl(), will call dm_blk_report_zones(). If\nblk_revalidate_disk_zones() fails, these resources can be freed while\nthe other process is still using them, causing a use-after-free error.\n\nblk_revalidate_disk_zones() will only ever be called when initially\nsetting up the zone append emulation resources, such as when setting up\na zoned dm-crypt table for the first time. Further table swaps will not\nset md->zone_revalidate_map or call blk_revalidate_disk_zones().\nHowever it must be called using the new table (referenced by\nmd->zone_revalidate_map) and the new queue limits while the DM device is\nsuspended. dm_blk_report_zones() needs some way to distinguish between a\ncall from blk_revalidate_disk_zones(), which must be allowed to use\nmd->zone_revalidate_map to access this not yet activated table, and all\nother calls to dm_blk_report_zones(), which should not be allowed while\nthe device is suspended and cannot use md->zone_revalidate_map, since\nthe zone resources might be freed by the process currently calling\nblk_revalidate_disk_zones().\n\nSolve this by tracking the process that sets md->zone_revalidate_map in\ndm_revalidate_zones() and only allowing that process to make use of it\nin dm_blk_report_zones().","publishedAt":"2025-07-03T08:35:42.787Z","updatedAt":"2026-08-05T11:59:51.188Z","severity":{"score":7.8,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"f211268ed1f9bdf48f06a3ead5f5d88437450579","status":"affected","lessThan":"f9c1bdf24615303d48a2d0fd629c88f3189563aa","versionType":"git"},{"version":"f211268ed1f9bdf48f06a3ead5f5d88437450579","status":"affected","lessThan":"d19bc1b4dd5f322980b1f05f79b2ea4f0db10920","versionType":"git"},{"version":"f211268ed1f9bdf48f06a3ead5f5d88437450579","status":"affected","lessThan":"37f53a2c60d03743e0eacf7a0c01c279776fef4e","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/md/dm-core.h","drivers/md/dm-zone.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.10","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.10","versionType":"semver"},{"version":"6.12.34","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.15.3","status":"unaffected","lessThanOrEqual":"6.15.*","versionType":"semver"},{"version":"6.16","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/md/dm-core.h","drivers/md/dm-zone.c"]}],"references":["https://git.kernel.org/stable/c/f9c1bdf24615303d48a2d0fd629c88f3189563aa","https://git.kernel.org/stable/c/d19bc1b4dd5f322980b1f05f79b2ea4f0db10920","https://git.kernel.org/stable/c/37f53a2c60d03743e0eacf7a0c01c279776fef4e"],"weaknesses":[],"ingestedAt":"2026-10-29T20:09:09.358Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2025/38xxx/CVE-2025-38141.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2025-38141","state":"PUBLISHED","datePublished":"2025-07-03T08:35:42.787Z","dateUpdated":"2026-08-05T11:59:51.188Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2025-04-16T04:51:23.987Z"},"containers":{"cna":{"title":"dm: fix dm_blk_report_zones","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndm: fix dm_blk_report_zones\n\nIf dm_get_live_table() returned NULL, dm_put_live_table() was never\ncalled. Also, it is possible that md->zone_revalidate_map will change\nwhile calling this function. Only read it once, so that we are always\nusing the same value. Otherwise we might miss a call to\ndm_put_live_table().\n\nFinally, while md->zone_revalidate_map is set and a process is calling\nblk_revalidate_disk_zones() to set up the zone append emulation\nresources, it is possible that another process, perhaps triggered by\nblkdev_report_zones_ioctl(), will call dm_blk_report_zones(). If\nblk_revalidate_disk_zones() fails, these resources can be freed while\nthe other process is still using them, causing a use-after-free error.\n\nblk_revalidate_disk_zones() will only ever be called when initially\nsetting up the zone append emulation resources, such as when setting up\na zoned dm-crypt table for the first time. Further table swaps will not\nset md->zone_revalidate_map or call blk_revalidate_disk_zones().\nHowever it must be called using the new table (referenced by\nmd->zone_revalidate_map) and the new queue limits while the DM device is\nsuspended. dm_blk_report_zones() needs some way to distinguish between a\ncall from blk_revalidate_disk_zones(), which must be allowed to use\nmd->zone_revalidate_map to access this not yet activated table, and all\nother calls to dm_blk_report_zones(), which should not be allowed while\nthe device is suspended and cannot use md->zone_revalidate_map, since\nthe zone resources might be freed by the process currently calling\nblk_revalidate_disk_zones().\n\nSolve this by tracking the process that sets md->zone_revalidate_map in\ndm_revalidate_zones() and only allowing that process to make use of it\nin dm_blk_report_zones()."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"f211268ed1f9bdf48f06a3ead5f5d88437450579","status":"affected","lessThan":"f9c1bdf24615303d48a2d0fd629c88f3189563aa","versionType":"git"},{"version":"f211268ed1f9bdf48f06a3ead5f5d88437450579","status":"affected","lessThan":"d19bc1b4dd5f322980b1f05f79b2ea4f0db10920","versionType":"git"},{"version":"f211268ed1f9bdf48f06a3ead5f5d88437450579","status":"affected","lessThan":"37f53a2c60d03743e0eacf7a0c01c279776fef4e","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/md/dm-core.h","drivers/md/dm-zone.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.10","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.10","versionType":"semver"},{"version":"6.12.34","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.15.3","status":"unaffected","lessThanOrEqual":"6.15.*","versionType":"semver"},{"version":"6.16","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/md/dm-core.h","drivers/md/dm-zone.c"]}],"references":[{"url":"https://git.kernel.org/stable/c/f9c1bdf24615303d48a2d0fd629c88f3189563aa"},{"url":"https://git.kernel.org/stable/c/d19bc1b4dd5f322980b1f05f79b2ea4f0db10920"},{"url":"https://git.kernel.org/stable/c/37f53a2c60d03743e0eacf7a0c01c279776fef4e"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The vulnerable function is reached through the BLKREPORTZONE/BLKREPORTZONEV2 ioctl on a device-mapper block device node (blkdev_common_ioctl → blkdev_report_zones_ioctl → blkdev_report_zones → dm_blk_report_zones), i.e. a local syscall on a local device file. No network or remote peer data is involved.\nAC:L - The attacker fully controls their side of the race and can spin the ioctl at thousands of calls per second, while the vulnerable window — a whole-device zone revalidation on an SMR/ZNS device plus the entire DM_TABLE_LOAD-to-resume gap where md->map is NULL — is wide and recurs on every zoned DM table setup, so no condition outside the attacker's influence has to fall into place.\nPR:L - BLKREPORTZONE is handled in blkdev_common_ioctl() with no capable() check and without requiring FMODE_WRITE, so any local user able to open the DM device read-only (disk-group member, container with the device exposed, or an unprivileged process on an embedded/Android zoned-storage system) can drive the ioctl loop.\nUI:N - The attacker only needs to loop on the ioctl; the zone revalidation and the loaded-but-unresumed table state occur automatically during normal device setup at boot, hotplug, or storage-daemon activity, with no victim action required.\nS:U - The use-after-free, out-of-bounds per-CPU increment, and hang are all confined to the kernel's own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - A racing report walks a dm_table freed by dm_table_destroy() and zone resources freed by disk_free_zone_resources(), reading freed struct dm_target/dm_table contents and returning the resulting zone descriptors to userspace via blkdev_copy_zone_to_user(), and the SRCU counter imbalance from the garbage srcu_idx lets grace periods end early and expose further freed objects.\nI:H - dm_blk_do_report_zones() loads and calls tgt->type->report_zones out of a freed dm_table, giving a control-flow hijack primitive once the slab is reclaimed, and srcu_read_unlock() with an uninitialized stack index performs an out-of-bounds this_cpu_inc() past srcu_ctrs[] into adjacent per-CPU memory.\nA:H - The missing dm_put_live_table() permanently leaks an SRCU read-side critical section, so every later synchronize_srcu(&md->io_barrier) — table swap, suspend, or device removal — blocks forever in an unkillable D state while holding md->suspend_lock, wedging dmsetup; independently, the use-after-free on the freed table produces an oops or panic."}]}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-08-05T11:59:51.188Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.10","versionEndExcluding":"6.12.34"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.10","versionEndExcluding":"6.15.3"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.10","versionEndExcluding":"6.16"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"id":"CVE-2025-38141","role":"CISA Coordinator","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"version":"2.0.3","timestamp":"2026-06-10T20:40:19.111521Z"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-06-11T17:53:37.417Z"}}]}}}