{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-98989","id":"CVE-2026-98989","title":"Linux kernel mount namespace cycle via recursive bind mounts","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnamespace: check a recursive bind mount for mount namespace loops\n\ndo_loopback() refuses to bind mount the file of a mount namespace that\nis as old as the caller's or older because a mount namespace that holds\na mount of its own file, or of an ancestor's, would cause a cycle. But\nit only checks the dentry the bind mount starts fr","descriptionLong":"In the Linux kernel, the following vulnerability has been resolved:\n\nnamespace: check a recursive bind mount for mount namespace loops\n\ndo_loopback() refuses to bind mount the file of a mount namespace that\nis as old as the caller's or older because a mount namespace that holds\na mount of its own file, or of an ancestor's, would cause a cycle. But\nit only checks the dentry the bind mount starts from. With MS_REC\neverything below it is copied and do_loopback() passes\nCL_COPY_MNT_NS_FILE so mount namespace files below the source are\ncopied.\n\nThat's fine for a source in the caller's own mount namespace. Every\nmount namespace file in there passed the same check when it was\nbind-mounted. It isn't fine for a source in another mount namespace.\nmay_copy_tree() accepts a bind mount of any nsfs or pidfs file no matter\nwhat mount namespace it lives in so that /proc/<pid>/ns/<ns> and pidfds\ncan be bind mounted. If we create a bind-mount stack of mount namespaces\nfile descriptors the kernel will copy them irrespective of their\nancestoral relationship to the mount namespace in question:\n\n  151 146 0:7 net:[4026531833] /tmp/nrc/y rw - nsfs nsfs rw\n  152 151 0:7 mnt:[4026532293] /tmp/nrc/y rw - nsfs nsfs rw\n\nMount 152 is a mount of the mount namespace file of mount namespace\n4026532293 inside mount namespace 4026532293. That namespace and every\nmount in it are leaked... All it takes is a process in an older mount\nnamespace that stacks the file and repeating it leaks without limit:\n\n  after control: Shmem:               380 kB\n  child: mount(/proc/self/fd/6, MS_BIND|MS_REC): ok\n  after cycle: Shmem:             65916 kB\n\ndo_move_mount() runs check_for_nsfs_mounts() over a detached tree for\nexactly that reason. Do the same for the copy before it is grafted.","published":"2026-10-23T12:20:08.366Z","updated":"2026-11-12T02:30:40.696062541Z","reserved":"2026-09-25T10:25:14.384Z","status":"Received","rejected":false,"assigner":"Linux","metric":null,"metrics":[],"rating":"unrated","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"e149ed2b805fefdccf7ccdfc19eca22fdd4514ac","lessThan":"b82f3c1131456537a514595c3991b62652507c9d","status":"affected","versionType":"git"},{"version":"e149ed2b805fefdccf7ccdfc19eca22fdd4514ac","lessThan":"a0ba48256f5dff6f75a45f8ce39fe57f21df1022","status":"affected","versionType":"git"},{"version":"e149ed2b805fefdccf7ccdfc19eca22fdd4514ac","lessThan":"37a82f400efa4d263542a5fa41755b21057f1e5d","status":"affected","versionType":"git"},{"version":"e149ed2b805fefdccf7ccdfc19eca22fdd4514ac","lessThan":"c640a01a78e42302879006ed7b7d5a9a943ba815","status":"affected","versionType":"git"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"3.19","status":"affected"},{"version":"0","lessThan":"3.19","status":"unaffected","versionType":"semver"},{"version":"6.12.117","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.57","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.2.11","lessThanOrEqual":"7.2.*","status":"unaffected","versionType":"semver"},{"version":"7.3","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":[],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/b82f3c1131456537a514595c3991b62652507c9d","tags":["web"]},{"url":"https://git.kernel.org/stable/c/a0ba48256f5dff6f75a45f8ce39fe57f21df1022","tags":["web"]},{"url":"https://git.kernel.org/stable/c/37a82f400efa4d263542a5fa41755b21057f1e5d","tags":["web"]},{"url":"https://git.kernel.org/stable/c/c640a01a78e42302879006ed7b7d5a9a943ba815","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98989.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98989","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":0.00168,"epssPercentile":0.06294,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-98989","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98989","ok":true,"note":"Received"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-98989","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-98989","ok":true,"note":"scored 2026-11-19"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}