All reports
Medium

kernel: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2025-38058

Probability of exploitation in the next 30 days: 0.20%

FIRST EPSS · 2026-11-20

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.

A flaw was found in the Linux kernel's filesystem subsystem. A local user can cause a Denial of Service (DoS) by triggering a system crash. This issue stems from a race condition during concurrent filesystem unmount and path traversal operations where mount states are checked without proper locking, leading to reference count desynchronization.