Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 16 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38058, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 48a066e72d970a3e225a9c18690d570c736fc455 – < 628fb00195ce21a90cf9e4e3d105cd9e58f77b40
    • affected 48a066e72d970a3e225a9c18690d570c736fc455 – < b89eb56a378b7b2c1176787fc228d0a57172bdd5
    • affected 48a066e72d970a3e225a9c18690d570c736fc455 – < f6d45fd92f62845cbd1eb5128fd8f0ed7d0c5a42
    • affected 48a066e72d970a3e225a9c18690d570c736fc455 – < 9b0915e72b3cf52474dcee0b24a2f99d93e604a3
    • affected 48a066e72d970a3e225a9c18690d570c736fc455 – < d8ece4ced3b051e656c77180df2e69e19e24edc1
    • affected 48a066e72d970a3e225a9c18690d570c736fc455 – < 8cafd7266fa02e0863bacbf872fe635c0b9725eb
    • affected 48a066e72d970a3e225a9c18690d570c736fc455 – < b55996939c71a3e1a38f3cdc6a8859797efc9083
    • affected 48a066e72d970a3e225a9c18690d570c736fc455 – < 250cf3693060a5f803c5f1ddc082bb06b16112a9
  • Linux · Linux

    • affected 3.13
    • unaffected < 3.13
    • unaffected 5.4.294 – ≤ 5.4.*
    • unaffected 5.10.238 – ≤ 5.10.*
    • unaffected 5.15.185 – ≤ 5.15.*
    • unaffected 6.1.141 – ≤ 6.1.*
    • unaffected 6.6.93 – ≤ 6.6.*
    • unaffected 6.12.31 – ≤ 6.12.*
    • unaffected 6.14.9 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38058 badge
[![CVE-2025-38058](https://cveledger.app/badge/CVE-2025-38058.svg)](https://cveledger.app/cve/CVE-2025-38058)

Record last updated .