SECUFOCUSNOW
Home›CVE index›CVE-2025-38172
Review reviewHigh

CVE-2025-38172

Linux Linux, linux kernel

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_fi...

CVSS
7.8
EPSS
0.15%
4.47% percentile
CISA KEV
Not listed
Published
2025.07.03
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.15%
Technical severityCVSS 7.8

Vulnerability overview

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_fi...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= fb176750266a3d7f42ebdcf28e8ba40350b27847 < 65115472f741ca000d7ea4a5922214f93cd1516e, >= fb176750266a3d7f42ebdcf28e8ba40350b27847 < cd04beb9ce2773a16057248bb4fa424068ae3807, >= fb176750266a3d7f42ebdcf28e8ba40350b27847 < 9748f2f54f66743ac77275c34886a9f890e18409, >= 6.12, >= 6.12 < 6.12.34, >= 6.13 < 6.15.3
Fixed versions
6.12.34, 6.15.3

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416