{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98993 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98993 is a high-severity vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98993 and fix it if it is affected.\n\nWhat it is: CVE-2026-98993 is a high-severity vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98993 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98993/ (Markdown: https://insights.sbomify.com/CVE-2026-98993/index.md)","id":"CVE-2026-98993","markdown":"https://insights.sbomify.com/CVE-2026-98993/index.md","name":"CVE-2026-98993","record":{"aliases":["AZL-110834","BELL-CVE-2026-98993","DEBIAN-CVE-2026-98993","GHSA-53w5-4v27-r5f4","UBUNTU-CVE-2026-98993"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnamespace: don't inherit MNT_UMOUNT in clone_mnt()\n\nMNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has\ntaken out of its namespace. It's never cleared. __detach_mounts()\nunhooks a mount that carries it instead of unmounting it.\n\ndisconnect_mount() lets an unmounted child stay attached only if its\nparent carries it. propagate_umount() takes it as the sign that a mount\nis going to be unmounted when it decides what else can be unmounted,\nwhere a chain of locked mounts ends and where a for reparenting an\novermount.\n\nclone_mnt() copies the flags of the source and only masks\nMNT_INTERNAL_FLAGS which doesn't include MNT_UMOUNT. A mount that was\nlazily unmounted but is kept alive by a file descriptor can still be\ncopied when its root is an nsfs or pidfs file because may_copy_tree()\naccepts those before checking whether the source is mounted at all:\n\n  mount --bind /proc/self/ns/net /tmp/x\n  exec 3\u003c /tmp/x\n  umount -l /tmp/x\n  mount --bind /proc/self/fd/3 /tmp/y\n\nThe mount on /tmp/y is attached to the caller's namespace with\nMNT_UMOUNT already set and every copy of it inherits the flag again.\n\nThat causes a number of bugs:\n\n- Unlink its mountpoint from a mount namespace where it isn't one.\n  __detach_mounts() takes it for a mount that was unmounted earlier,\n  unhooks it from its parent and drops the reference the namespace\n  holds on it. It stays in the namespace with one reference too few\n  and as its own parent, so it can't be unmounted through the file\n  descriptor anymore and the namespace never finds it again. When the\n  namespace goes away it's leaked and points to a freed struct\n  mnt_namespace that may_change_propagation() and anon_ns_root() read\n  on the next propagation change or mount_setattr() through the file\n  descriptor.\n\n- Make it shared and unmount a peer. trace_transfers() follows the\n  flag from the peer into it and strips it from its peer group.\n\n- Let a propagated umount reach it. gather_candidates() marks it with\n  T_UMOUNT_CANDIDATE but never puts it on the candidate list, so the\n  mark is never cleared and every later propagated umount skips it. If\n  it's the parent of a locked mount handle_locked() takes it as the\n  cutoff and commits the locked child that should have stayed and\n  disconnect_mount() leaves that child attached to it, unmounted under\n  a mounted parent, which is what disconnect_mount() exists to\n  prevent. When the namespace goes away umount_tree() visits the child\n  a second time. And once __detach_mounts() has made it its own parent\n  reparent() never finds the end of the chain of unmounted parents.\n\nA clone is a new mount that has never been unmounted. Add MNT_UMOUNT\nto MNT_INTERNAL_FLAGS so clone_mnt() never copies it. And warn when\numount_tree() reaches a mount that already has it set.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"namespace: don't inherit MNT_UMOUNT in clone_mnt()","id":"CVE-2026-98993","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"statmount: read the parent of an unmounted mount under mount_lock","id":"CVE-2026-98994"},"packages":[],"prev":{"headline":"namespace: don't copy an unmounted mount tree","id":"CVE-2026-98992"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-24","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98993/"}