CVE-2025-38172 Details
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.
A use-after-free vulnerability has been identified in the Linux kernel's EROFS (Enhanced Read-Only File System) implementation. This issue arises when multiple devices of different types are used simultaneously. The function 'erofs_init_device' ensures that if the primary device is file-backed, extra devices must also be regular files. However, a problem occurs when the primary device is a block device and the extra one is file-backed. In this scenario, 'erofs_init_device' returns an ENOTBLK error, which is not properly handled in 'erofs_fc_get_tree'. This oversight leads to a use-after-free condition, as the superblock information is not correctly initialized before the primary device is deactivated and freed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/65115472f741ca000d7ea4a5922214f93cd1516e | kernel.org | Patch |
| https://git.kernel.org/stable/c/9748f2f54f66743ac77275c34886a9f890e18409 | kernel.org | Patch |
| https://git.kernel.org/stable/c/cd04beb9ce2773a16057248bb4fa424068ae3807 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.12, < 6.12.34 >= 6.13, < 6.15.3 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 20, 2025 | Initial Analysis | [email protected] |
| Jul 3, 2025 | New CVE Received | kernel.org |