The Linux kernel bug stems from an incorrect implementation of propagate_mount_busy(), which fails to detect when a mount that is being unmounted is still referenced by other copies in a propagation chain. In such cases, a synchronous umount call succeeds even though the mount remains in use, leaving dangling file descriptors and potentially exposing or removing critical filesystem mounts. This can be exploited by a container or privileged process to unmount a mount in the host namespace, causing data loss, service interruption, or privilege escalation if the mount protected sensitive information. The bug illustrates a failure to enforce pre‑condition checks on resource usage and could lead to denial of service or unauthorized access.

The vulnerability is present in the Linux kernel; specific affected versions are not listed in the advisory, so all kernel releases from the time of the patch until at least the upstream change are potentially impacted. The advisory notes that a container can observe the issue through shared mounts and relative propagation, implying that any environment exposing mount propagation semantics to untrusted code may be at risk.

The CVSS score of 2.5 indicates low severity. An EPSS score of 0.00167 reveals a very low exploitation probability. The vulnerability is not listed in CISA's KEV catalog. Exploitation requires local privilege or control over mount namespaces; likely vectors involve containers that manipulate mounts with "unshare", "mount --make‑slave", or "move_mount" operations. The risk is low in terms of severity and probability, but accidental removal of critical mounts can cause denial of service or, if the mount protected sensitive data, potential privilege escalation.