CVE-2026-98983

Not scored yetLast modified Oct 23, 2026

Description

In the Linux kernel, the following vulnerability has been resolved:

unshare: don't drop active namespace references that were never taken

Active references on the namespaces of an nsproxy are taken when the nsproxy is installed into a task in switch_task_namespaces() and copy_namespaces() and dropped again by put_nsproxy() through deactivate_nsproxy().

But ksys_unshare() calls put_nsproxy() on an nsproxy that was never installed when set_cred_ucounts() fails. The new namespaces of that nsproxy go from zero to minus one and the namespaces shared with the caller lose a reference that belongs to the nsproxy the caller keeps using:

WARNING: kernel/nscommon.c:171 at __ns_ref_active_put+0x1cd/0x230 nsproxy_ns_active_put deactivate_nsproxy ksys_unshare

Afterwards the namespaces the caller lives in aren't listed by listns() anymore. set_cred_ucounts() only fails when alloc_ucounts() can't allocate and it only allocates when the real uid of the caller differs from its effective uid.

Commit cefd55bd2159 ("nsproxy: fix free_nsproxy() and simplify create_new_namespaces()") separated the two cases on purpose. nsproxy_free() frees an nsproxy that was prepared but never installed and that's what a failed setns() uses in put_nsset(). Export it and use it for a failed unshare() as well.

Metrics

No CVSS score has been published yet.

Affected software

Source: the vendor's advisory (CNA). NVD analysis pending.

VendorProductVersions
LinuxLinux>= a98621a0f187a934c115dcfe79a49520ae892111, < 56fe03a0c05dba4c5f6a23c391f96de1614a098c; >= a98621a0f187a934c115dcfe79a49520ae892111, < 0b6f31a3c0b16066f812e94b52a704174a6f23cd; 27ae6b17c9ba7ff353ab0906297f08aa845782b4; 297261b343371c4f0b31055d53d285138ec21565; 813a47b0309097da71781ee4ac11922e39b67d55; 6e608e3e5ce12ce7fd21e46212eccca37f917d0e; a261fccdb4ac58ec5ba6aa1d92a6cc418fff301f; 665dc1ed16357988d439fc5bbc860ee36f540d81; >= 5.15.209, < 5.16; >= 6.1.175, < 6.2; >= 6.6.141, < 6.7; >= 6.12.91, < 6.13; >= 6.18.33, < 6.19; >= 7.0.10, < 7.1
LinuxLinux7.1

References

Timeline

Published
Oct 23, 2026
Last modified
Oct 23, 2026
NVD status
Received

Related CVEs from 2026

CVE-2026-98984In the Linux kernel, the following vulnerability has been resolved: dcache: don't put a mountpoint on a dentry that's being removed rmdir(CVE-2026-98985In the Linux kernel, the following vulnerability has been resolved: namespace: check the mounts before reading their parents in pivot_root(CVE-2026-98986In the Linux kernel, the following vulnerability has been resolved: namespace: remove the fsnotify marks of a mount namespace in process coCVE-2026-98987In the Linux kernel, the following vulnerability has been resolved: namespace: look at the topmost mount for a mount namespace file attachCVE-2026-989888.8In the Linux kernel, the following vulnerability has been resolved: namespace: keep covered mounts covered in OPEN_TREE_NAMESPACE open_treCVE-2026-98989In the Linux kernel, the following vulnerability has been resolved: namespace: check a recursive bind mount for mount namespace loops do_lCVE-2026-98998.3Use after free in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potenCVE-2026-98990In the Linux kernel, the following vulnerability has been resolved: namespace: check a submount for references right before unmounting it CVE-2026-989917.8In the Linux kernel, the following vulnerability has been resolved: namespace: queue a mount only once for mount notifications mnt_notify_CVE-2026-98992In the Linux kernel, the following vulnerability has been resolved: namespace: don't copy an unmounted mount tree may_copy_tree() accepts CVE-2026-989937.8In the Linux kernel, the following vulnerability has been resolved: namespace: don't inherit MNT_UMOUNT in clone_mnt() MNT_UMOUNT gets raiCVE-2026-98994In the Linux kernel, the following vulnerability has been resolved: statmount: read the parent of an unmounted mount under mount_lock stat
CVE-2026-98983: Unscored | Vulnix