Linux Kernel up to 6.14.8 __legitimize_mnt locking

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.14.8 and classified as problematic. Impacted is the function __legitimize_mnt. This manipulation causes an unknown weakness. The identification of this vulnerability is CVE-2025-38058. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 6.14.8 and classified as problematic. The CWE definition for the vulnerability is CWE-667. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. The impact remains unknown. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2025-38058 since 04/16/2025. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 241773 (Amazon Linux 2023 : bpftool, kernel6.12, kernel6.12-modules-extra (ALAS2023-2025-1052)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.4.294, 5.10.238, 5.15.185, 6.1.141, 6.6.93, 6.12.31 or 6.14.9 eliminates this vulnerability. Applying the patch 628fb00195ce21a90cf9e4e3d105cd9e58f77b40/b89eb56a378b7b2c1176787fc228d0a57172bdd5/f6d45fd92f62845cbd1eb5128fd8f0ed7d0c5a42/9b0915e72b3cf52474dcee0b24a2f99d93e604a3/d8ece4ced3b051e656c77180df2e69e19e24edc1/8cafd7266fa02e0863bacbf872fe635c0b9725eb/b55996939c71a3e1a38f3cdc6a8859797efc9083/250cf3693060a5f803c5f1ddc082bb06b16112a9 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (241773) and CERT Bund (WID-SEC-2025-1350). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • Dell Avamar
  • Dell NetWorker
  • Dell Secure Connect Gateway
  • IBM QRadar SIEM

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Locking
CWE: CWE-667
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 241773
Nessus Name: Amazon Linux 2023 : bpftool, kernel6.12, kernel6.12-modules-extra (ALAS2023-2025-1052)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 5.4.294/5.10.238/5.15.185/6.1.141/6.6.93/6.12.31/6.14.9
Patch: 628fb00195ce21a90cf9e4e3d105cd9e58f77b40/b89eb56a378b7b2c1176787fc228d0a57172bdd5/f6d45fd92f62845cbd1eb5128fd8f0ed7d0c5a42/9b0915e72b3cf52474dcee0b24a2f99d93e604a3/d8ece4ced3b051e656c77180df2e69e19e24edc1/8cafd7266fa02e0863bacbf872fe635c0b9725eb/b55996939c71a3e1a38f3cdc6a8859797efc9083/250cf3693060a5f803c5f1ddc082bb06b16112a9

Timelineinfo

04/16/2025 🔍
06/18/2025 +63 days 🔍
06/18/2025 +0 days 🔍
02/18/2026 +245 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-38058 (🔍)
GCVE (CVE): GCVE-0-2025-38058
GCVE (VulDB): GCVE-100-312889
CERT Bund: WID-SEC-2025-1350 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Entryinfo

Created: 06/18/2025 12:11
Updated: 02/18/2026 20:07
Changes: 06/18/2025 12:11 (56), 07/11/2025 13:54 (2), 12/19/2025 00:31 (12), 02/18/2026 20:07 (7)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!