{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98976 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98976 is a high-severity vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98976 and fix it if it is affected.\n\nWhat it is: CVE-2026-98976 is a high-severity vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98976 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-98976/ (Markdown: https://insights.sbomify.com/CVE-2026-98976/index.md)","id":"CVE-2026-98976","markdown":"https://insights.sbomify.com/CVE-2026-98976/index.md","name":"CVE-2026-98976","record":{"aliases":["DEBIAN-CVE-2026-98976","GHSA-38fm-jc3c-v2pm","UBUNTU-CVE-2026-98976"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnamespace: keep the lock on a mount that a propagated copy is moved beneath\n\nattach_recursive_mnt() transfers MNT_LOCKED from the top mount to the\nmount that is moved beneath it with MOVE_MOUNT_BENEATH. This allows the\nowner of a user namespace to replace its locked /proc or its root. The\nmount beneath takes on the job of covering the underlying mountpoint\nallowing the top mount to be unmounted.\n\nConsider two mount namespaces:\n\n(H) The host H has a shared mount P with a secret in P/d\n(Z) Z is a user namespace made from M. Its copy of P receives\n    propagation from the host's P and its copy of M's cover on P/d is\n    locked Z's owner must not get to see P/d.\n\nNow (H) mounts X on P/d. This propagates into (Z). The copy of X lands\nbeneath (Z)'s locked cover. The locked property is transfered from (Z)'s\ncover to the copy of X propagated beneath it. The cover is now unlocked.\n\nNow (H) unmounts X again. The copy of X in (Z) gets unmounted and the\ncovering mount is left unlocked on top of P/d. (Z) can now unmount it:\n\n    Z: umount2(P/d)             = EINVAL            /* the cover is locked */\n    H: mount X on P/d, umount X                     /* both propagate into Z /*\n    Z: umount2(P/d)             = 0                 /* the cover is now unlocked */\n    Z: read P/d/secret          = \"covered-by-root\" /* secret revealed */\n\nSo only transfer the locked property to the mount beneath for mounts the\ncaller has placed. A propagated copy that lands beneath a locked mount\nis locked as well so that the mount at the bottom of the stack carries a\nlock the way every check expects. The mount on top of it remains locked\nto ensure that it keeps covering even if the propagated mount is\nunmounted again.","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: keep the lock on a mount that a propagated copy is moved beneath","id":"CVE-2026-98976","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"namespace: handle mount locking for automounts correctly","id":"CVE-2026-98977"},"packages":[],"prev":{"headline":"xfs: stop exchanging reflink flags when exchanging mappings","id":"CVE-2026-98975"},"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-98976/"}