VulnWatch by ve1ve2

CVE-2026-98989

unknown awaiting NVD score — see report severities below NVD ↗CVE.org ↗

In the Linux kernel, the following vulnerability has been resolved: namespace: check a recursive bind mount for mount namespace loops do_loopback() refuses to bind mount the file of a mount namespace that is as old as the caller's or older because a mount namespace that holds a mount of its own file, or of an ancestor's, would cause a cycle. But it only checks the dentry the bind mount starts from. With MS_REC everything below it is copied and do_loopback() passes CL_COPY_MNT_NS_FILE so mount namespace files below the source are copied. That's fine for a source in the caller's own mount namespace. Every mount namespace file in there passed the same check when it was bind-mounted. It isn't fine for a source in another mount namespace. may_copy_tree() accepts a bind mount of any nsfs or pidfs file no matter what mount namespace it lives in so that /proc/<pid>/ns/<ns> and pidfds can be bind mounted. If we create a bind-mount stack of mount namespaces file descriptors the kernel will co

CVSS:
—
EPSS:
0.17% (percentile 6.2)
Published:
Modified:
First seen:
NVD status:
Received
Aliases:
CVE-2026-100080, CVE-2026-100081, CVE-2026-100082, CVE-2026-89866, CVE-2026-92499, CVE-2026-98176, CVE-2026-98177, CVE-2026-98180, CVE-2026-98228, CVE-2026-98408, CVE-2026-98439, CVE-2026-98449, CVE-2026-98466, CVE-2026-98674, CVE-2026-98682, CVE-2026-98683, CVE-2026-98684, CVE-2026-98685, CVE-2026-98714, CVE-2026-98715, CVE-2026-98786, CVE-2026-98853, CVE-2026-98863, CVE-2026-98920, CVE-2026-98978, CVE-2026-98996, CVE-2026-99021, CVE-2026-99026, CVE-2026-99076, CVE-2026-99086, CVE-2026-99087, CVE-2026-99109, CVE-2026-99122, CVE-2026-99146, CVE-2026-99172, CVE-2026-99270, CVE-2026-99271, CVE-2026-99273, CVE-2026-99274, CVE-2026-99281, CVE-2026-99282, CVE-2026-99283, CVE-2026-99286, CVE-2026-99287, CVE-2026-99288, CVE-2026-99290, CVE-2026-99292, CVE-2026-99295, CVE-2026-99296

JSON

Reports (2)