CVE-2025-38141

Description

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

Predictions

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No vendor mitigations ingested yet for this CVE. The mitigation-content worker queues fetches as references arrive — check back in a few minutes, or see the references list below.

References

• https://access.redhat.com/errata/RHSA-2026:1143
• https://www.suse.com/security/cve/CVE-2025-38141.html
• https://errata.rockylinux.org/RLSA-2026:1143
• https://security-tracker.debian.org/tracker/CVE-2025-38141
• https://bugzilla.redhat.com/2376052
• https://bugzilla.redhat.com/2381870
• https://bugzilla.redhat.com/2393488
• https://bugzilla.redhat.com/2418872
• https://bugzilla.redhat.com/2418876
• https://bugzilla.redhat.com/2419891
• https://bugzilla.redhat.com/2422836
• https://bugzilla.redhat.com/2422840
• https://errata.almalinux.org/9/ALSA-2026-1143.html

💬 Discuss CVE-2025-38141 on VIR Community →

Community-verified mitigations for this CVE will appear above when contributors publish them.