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.
References (11)
Core 11
Core References
Third Party Advisory
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
Vendor Advisory
https://cert-portal.siemens.com/productcert/html/ssa-082556.html
Scores
CVSS v3
5.5
EPSS
0.0013
EPSS Percentile
2.9%
Attack Vector
LOCAL
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Details
CWE
CWE-667
Status
published
Products (28)
debian/debian_linux
11.0
linux/Kernel
3.13.0 - 5.4.294linux
linux/Kernel
5.11.0 - 5.15.185linux
linux/Kernel
5.16.0 - 6.1.141linux
linux/Kernel
5.5.0 - 5.10.238linux
linux/Kernel
6.13.0 - 6.14.9linux
linux/Kernel
6.2.0 - 6.6.93linux
linux/Kernel
6.7.0 - 6.12.31linux
Linux/Linux
< 3.13
Linux/Linux
3.13
... and 18 more
Published
Jun 18, 2025
Tracked Since
Feb 18, 2026