{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98985 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98985 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98985 and fix it if it is affected.\n\nWhat it is: CVE-2026-98985 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98985 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-98985/ (Markdown: https://insights.sbomify.com/CVE-2026-98985/index.md)","id":"CVE-2026-98985","markdown":"https://insights.sbomify.com/CVE-2026-98985/index.md","name":"CVE-2026-98985","record":{"aliases":["AZL-110822","BELL-CVE-2026-98985","DEBIAN-CVE-2026-98985","GHSA-gfp5-4w3q-vwjx","UBUNTU-CVE-2026-98985"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnamespace: check the mounts before reading their parents in pivot_root()\n\npath_pivot_root() reads the parents of new_root and of the caller's root\nand checks whether they are shared before it checks that either mount is\nin the caller's mount namespace. Only namespace_sem is held. That's fine\nfor a mount that is in the caller's mount namespace.\n\nBut new_root can be a file descriptor to a mount that has been unmounted\nand that only the file descriptor keeps alive. If that mount stayed\nattached to its parent when it was unmounted nothing pins the parent for\nit. The final mntput() of the parent unhooks the children under\nmount_lock alone and frees the parent afterwards:\n\n  pivot_root()                     close(fd), last ref on the parent\n  ------------                     ---------------------------------\n  ex_parent = new_mnt-\u003emnt_parent\n                                   mntput_no_expire_slowpath()\n                                     __umount_mnt(new_mnt)\n                                   cleanup_mnt()\n                                     call_rcu()\n  IS_MNT_SHARED(ex_parent)\n\n  BUG: KASAN: slab-use-after-free in path_pivot_root+0xf1a/0x1840\n  Read of size 4 at addr ffff8881047382f8 by task pivot_widen/157\n   path_pivot_root+0xf1a/0x1840\n   __x64_sys_pivot_root+0x165/0x190\n\nThe same goes for the caller's root via chroot(). Both outcomes of the\ncheck end in EINVAL so nothing but the read itself goes wrong. It's the\nsame thing commit bb4609405752 (\"statmount: read the parent of an\nunmounted mount under mount_lock\") fixed for statmount().\n\nCheck that both mounts are in the caller's namespace before their\nparents are read. Every path returns EINVAL either way.","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: check the mounts before reading their parents in pivot_root()","id":"CVE-2026-98985","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"namespace: remove the fsnotify marks of a mount namespace in process context","id":"CVE-2026-98986"},"packages":[],"prev":{"headline":"dcache: don't put a mountpoint on a dentry that's being removed","id":"CVE-2026-98984"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98985/"}