{"id":"CVE-2026-98983","published":"2026-10-23T13:17:20.160","lastModified":"2026-10-23T13:17:20.160","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nunshare: don't drop active namespace references that were never taken\n\nActive references on the namespaces of an nsproxy are taken when the\nnsproxy is installed into a task in switch_task_namespaces() and\ncopy_namespaces() and dropped again by put_nsproxy() through\ndeactivate_nsproxy().\n\nBut ksys_unshare() calls put_nsproxy() on an nsproxy that was never\ninstalled when set_cred_ucounts() fails. The new namespaces of that\nnsproxy go from zero to minus one and the namespaces shared with the\ncaller lose a reference that belongs to the nsproxy the caller keeps\nusing:\n\n  WARNING: kernel/nscommon.c:171 at __ns_ref_active_put+0x1cd/0x230\n   nsproxy_ns_active_put\n   deactivate_nsproxy\n   ksys_unshare\n\nAfterwards the namespaces the caller lives in aren't listed by listns()\nanymore. set_cred_ucounts() only fails when alloc_ucounts() can't\nallocate and it only allocates when the real uid of the caller differs\nfrom its effective uid.\n\nCommit cefd55bd2159 (\"nsproxy: fix free_nsproxy() and simplify\ncreate_new_namespaces()\") separated the two cases on purpose.\nnsproxy_free() frees an nsproxy that was prepared but never installed\nand that's what a failed setns() uses in put_nsset(). Export it and use\nit for a failed unshare() as well.","cvssScore":null,"cvssSeverity":null,"cvssVector":null,"cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/0b6f31a3c0b16066f812e94b52a704174a6f23cd","tags":[]},{"url":"https://git.kernel.org/stable/c/56fe03a0c05dba4c5f6a23c391f96de1614a098c","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":null}