1. Home
  2. Vulnerabilities
  3. CVE-2025-38058
5.5
MEDIUM CVSS 3.1
CVE-2025-38058
__legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock
Description

In the Linux kernel, the following vulnerability has been resolved: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock ... or we risk stealing final mntput from sync umount - raising mnt_count after umount(2) has verified that victim is not busy, but before it has set MNT_SYNC_UMOUNT; in that case __legitimize_mnt() doesn't see that it's safe to quietly undo mnt_count increment and leaves dropping the reference to caller, where it'll be a full-blown mntput(). Check under mount_lock is needed; leaving the current one done before taking that makes no sense - it's nowhere near common enough to bother with.

INFO

Published Date :

June 18, 2025, 10:15 a.m.

Last Modified :

Dec. 18, 2025, 9:32 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2025-38058 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
1 Debian debian_linux
: Total Affected Vendor : 2 | Products : 2
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
Apply the Linux kernel patch to fix the mount synchronization issue.
  • Update the Linux kernel to the latest secure version.
  • Recompile the kernel with the provided patch.
  • Deploy the updated kernel to affected systems.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2025-38058.

URL Resource
https://git.kernel.org/stable/c/250cf3693060a5f803c5f1ddc082bb06b16112a9 Patch
https://git.kernel.org/stable/c/628fb00195ce21a90cf9e4e3d105cd9e58f77b40 Patch
https://git.kernel.org/stable/c/8cafd7266fa02e0863bacbf872fe635c0b9725eb Patch
https://git.kernel.org/stable/c/9b0915e72b3cf52474dcee0b24a2f99d93e604a3 Patch
https://git.kernel.org/stable/c/b55996939c71a3e1a38f3cdc6a8859797efc9083 Patch
https://git.kernel.org/stable/c/b89eb56a378b7b2c1176787fc228d0a57172bdd5 Patch
https://git.kernel.org/stable/c/d8ece4ced3b051e656c77180df2e69e19e24edc1 Patch
https://git.kernel.org/stable/c/f6d45fd92f62845cbd1eb5128fd8f0ed7d0c5a42 Patch
https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html Third Party Advisory
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html Third Party Advisory
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-38058 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-38058 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-38058 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2025-38058 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Dec. 18, 2025

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
    Added CWE CWE-667
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:6.15:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.15:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.15:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.238 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 5.4.294 *cpe:2.3:o:linux:linux_kernel:6.15:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.15:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.14.9 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.31 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.185 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.141 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.93
    Added CPE Configuration OR *cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/250cf3693060a5f803c5f1ddc082bb06b16112a9 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/628fb00195ce21a90cf9e4e3d105cd9e58f77b40 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/8cafd7266fa02e0863bacbf872fe635c0b9725eb Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/9b0915e72b3cf52474dcee0b24a2f99d93e604a3 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/b55996939c71a3e1a38f3cdc6a8859797efc9083 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/b89eb56a378b7b2c1176787fc228d0a57172bdd5 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/d8ece4ced3b051e656c77180df2e69e19e24edc1 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/f6d45fd92f62845cbd1eb5128fd8f0ed7d0c5a42 Types: Patch
    Added Reference Type CVE: https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html Types: Third Party Advisory
    Added Reference Type CVE: https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html Types: Third Party Advisory
  • CVE Modified by af854a3a-2127-422b-91ae-364da2661108

    Nov. 03, 2025

    Action Type Old Value New Value
    Added Reference https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
    Added Reference https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jun. 18, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock ... or we risk stealing final mntput from sync umount - raising mnt_count after umount(2) has verified that victim is not busy, but before it has set MNT_SYNC_UMOUNT; in that case __legitimize_mnt() doesn't see that it's safe to quietly undo mnt_count increment and leaves dropping the reference to caller, where it'll be a full-blown mntput(). Check under mount_lock is needed; leaving the current one done before taking that makes no sense - it's nowhere near common enough to bother with.
    Added Reference https://git.kernel.org/stable/c/250cf3693060a5f803c5f1ddc082bb06b16112a9
    Added Reference https://git.kernel.org/stable/c/628fb00195ce21a90cf9e4e3d105cd9e58f77b40
    Added Reference https://git.kernel.org/stable/c/8cafd7266fa02e0863bacbf872fe635c0b9725eb
    Added Reference https://git.kernel.org/stable/c/9b0915e72b3cf52474dcee0b24a2f99d93e604a3
    Added Reference https://git.kernel.org/stable/c/b55996939c71a3e1a38f3cdc6a8859797efc9083
    Added Reference https://git.kernel.org/stable/c/b89eb56a378b7b2c1176787fc228d0a57172bdd5
    Added Reference https://git.kernel.org/stable/c/d8ece4ced3b051e656c77180df2e69e19e24edc1
    Added Reference https://git.kernel.org/stable/c/f6d45fd92f62845cbd1eb5128fd8f0ed7d0c5a42
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
Base CVSS Score: 5.5
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality Impact
Integrity Impact
Availability Impact