CVE-2026-98983unshare: don't drop active namespace references that were never taken
- —Not scoredno CVSS score yet
- 0.16%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 28 days later
· 28 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.16% · top 94% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected a98621a0f187a934c115dcfe79a49520ae892111 – < 56fe03a0c05dba4c5f6a23c391f96de1614a098c
- affected a98621a0f187a934c115dcfe79a49520ae892111 – < 0b6f31a3c0b16066f812e94b52a704174a6f23cd
- affected 27ae6b17c9ba7ff353ab0906297f08aa845782b4
- affected 297261b343371c4f0b31055d53d285138ec21565
- affected 813a47b0309097da71781ee4ac11922e39b67d55
- affected 6e608e3e5ce12ce7fd21e46212eccca37f917d0e
- affected a261fccdb4ac58ec5ba6aa1d92a6cc418fff301f
- affected 665dc1ed16357988d439fc5bbc860ee36f540d81
- affected 5.15.209 – < 5.16
- affected 6.1.175 – < 6.2
- affected 6.6.141 – < 6.7
- affected 6.12.91 – < 6.13
- affected 6.18.33 – < 6.19
- affected 7.0.10 – < 7.1
- affected 7.1
- unaffected < 7.1
- unaffected 7.2.11 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-108777 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98983)Record last updated .