CVE-2025-38172
Last modified
CVE-2025-38172 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: erofs: avoid using multiple devices with different type For multiple devices, both primary and extra devices should be the same type. `erofs_init_device` has already guaranteed that if the primary is a file-backed device, extra devices should also be regular files. However, if the primary is a block device while the extra device is a file-backed device, `erofs_init_device` will get an ENOTBLK, which is not treated as an error in `erofs_fc_get_tree`, and that leads to an UAF: erofs_fc_get_tree get_tree_bdev_flags(erofs_fc_fill_super) erofs_read_superblock erofs_init_device // sbi->dif0 is not inited yet, // return -ENOTBLK deactivate_locked_super free(sbi) if (err is -ENOTBLK) sbi->dif0.file = filp_open() // sbi UAF So if -ENOTBLK is hitted in `erofs_init_device`, it means the primary device must be a block device, and the extra device is not a block device. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: erofs: avoid using multiple devices with different type For multiple devices, both primary and extra devices should be the same type. `erofs_init_device` has already guaranteed that if the primary is a file-backed device, extra devices should also be regular files. However, if the primary is a block device while the extra device is a file-backed device, `erofs_init_device` will get an ENOTBLK, which is not treated as an error in `erofs_fc_get_tree`, and that leads to an UAF: erofs_fc_get_tree get_tree_bdev_flags(erofs_fc_fill_super) erofs_read_superblock erofs_init_device // sbi->dif0 is not inited yet, // return -ENOTBLK deactivate_locked_super free(sbi) if (err is -ENOTBLK) sbi->dif0.file = filp_open() // sbi UAF So if -ENOTBLK is hitted in `erofs_init_device`, it means the primary device must be a block device, and the extra device is not a block device. The error can be converted to -EINVAL.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.12, < 6.12.34 |
| Linux | Linux Kernel | >= 6.13, < 6.15.3 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38172?
How severe is CVE-2025-38172?
How do I fix CVE-2025-38172?
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-38167In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38168In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38169In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3817A vulnerability, which was classified as critical, has been …8.8
- CVE-2025-38170In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38171In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38173In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38174In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38175In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38176In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38177In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38178Rejected reason: This CVE ID has been rejected or withdrawn …
Are you affected by CVE-2025-38172?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
