CVE-2025-38058

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.

CVSS 3.1

5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS

0.2% chance of exploitation in the next 30 days; higher than 6% of CVEs (scores of 2026-10-25)

CWE

CWE-667

Published

2025-06-18

Modified

2026-10-15

Record from

the NVD, synced 2026-10-19

Affected

• debian:debian_linux
• linux:linux_kernel

References

• https://git.kernel.org/stable/c/250cf3693060a5f803c5f1ddc082bb06b16112a9
• https://git.kernel.org/stable/c/628fb00195ce21a90cf9e4e3d105cd9e58f77b40
• https://git.kernel.org/stable/c/8cafd7266fa02e0863bacbf872fe635c0b9725eb
• https://git.kernel.org/stable/c/9b0915e72b3cf52474dcee0b24a2f99d93e604a3
• https://git.kernel.org/stable/c/b55996939c71a3e1a38f3cdc6a8859797efc9083

Check your stackJSON