CVE-2025-38140
Last modified
CVE-2025-38140 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: dm: limit swapping tables for devices with zone write plugs dm_revalidate_zones() only allowed new or previously unzoned devices to call blk_revalidate_disk_zones(). If the device was already zoned, disk->nr_zones would always equal md->nr_zones, so dm_revalidate_zones() returned without doing any work. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: dm: limit swapping tables for devices with zone write plugs dm_revalidate_zones() only allowed new or previously unzoned devices to call blk_revalidate_disk_zones(). If the device was already zoned, disk->nr_zones would always equal md->nr_zones, so dm_revalidate_zones() returned without doing any work. This would make the zoned settings for the device not match the new table. If the device had zone write plug resources, it could run into errors like bdev_zone_is_seq() reading invalid memory because disk->conv_zones_bitmap was the wrong size. If the device doesn't have any zone write plug resources, calling blk_revalidate_disk_zones() will always correctly update device. If blk_revalidate_disk_zones() fails, it can still overwrite or clear the current disk->nr_zones value. In this case, DM must restore the previous value of disk->nr_zones, so that the zoned settings will continue to match the previous value that it fell back to. If the device already has zone write plug resources, blk_revalidate_disk_zones() will not correctly update them, if it is called for arbitrary zoned device changes. Since there is not much need for this ability, the easiest solution is to disallow any table reloads that change the zoned settings, for devices that already have zone plug resources. Specifically, if a device already has zone plug resources allocated, it can only switch to another zoned table that also emulates zone append. Also, it cannot change the device size or the zone size. A device can switch to an error target.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.14, < 6.15.3 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-38140?
How severe is CVE-2025-38140?
How do I fix CVE-2025-38140?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38135In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38136In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38137In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38138In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38139In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-3814The Tax Switch for WooCommerce plugin for WordPress is vulne…6.4
- CVE-2025-38141In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38142In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38143In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38144In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38145In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38146In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2025-38140?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
