CVE-2026-89766pidfd: hold exec_update_lock around namespace ioctl
- —Not scoredno CVSS score yet
- 0.19%Exploitation in 30 daysEPSS · top 91% 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: pidfd: hold exec_update_lock around namespace ioctl The PIDFD_GET_*_NAMESPACE ioctls in pidfd_ioctl() perform a filesystem credentials ptrace access check before handing out a namespace file descriptor. The accompanying comment states that the code "mirrors nsfs behavior", but, unlike the corresponding procfs paths, it does so without holding the target task's exec_update_lock. proc_ns_get_link() and proc_ns_readlink() both take exec_update_lock for reading around the ptrace check and the namespace lookup, so that the credentials used for the access decision match those of the task when its namespace is read. Without it, a caller can pass the check against the target's old credentials and then read the namespace after the target has execve()'d a setuid binary and committed new credentials -- accessing namespace information it should have been denied. Hold exec_update_lock for reading around the ptrace check and the namespace lookup so that pidfd truly mirrors nsfs behavior, as the comment already claims. open_namespace() itself runs outside the lock: once a namespace reference is obtained it carries its own refcount and is opened with the caller's own credentials, so a concurrent execve() on the target can no longer affect the outcome.
Timeline
ID reserved
By Linux
Published
- 38 days later
· 38 days later
Record updated
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.19% · top 91% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 5b08bd408534bfb3a7cf5778da5b27d4e4fffe12 – < bac2f1913a216677c2c220d7bb352dd0330065ca
- affected 5b08bd408534bfb3a7cf5778da5b27d4e4fffe12 – < cf24ce48d60225fdbee68ed2058763a1fd172ff3
- affected 5b08bd408534bfb3a7cf5778da5b27d4e4fffe12 – < e89318aa8629969e86548b05e7c19283af3f0efb
- affected 5b08bd408534bfb3a7cf5778da5b27d4e4fffe12 – < 9688a46802939da28f00cb40e8129615d5d4af39
- affected 6.11
- unaffected < 6.11
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/bac2f1913a216677c2c220d7bb352dd0330065ca (opens in a new tab)
- https://git.kernel.org/stable/c/cf24ce48d60225fdbee68ed2058763a1fd172ff3 (opens in a new tab)
- https://git.kernel.org/stable/c/e89318aa8629969e86548b05e7c19283af3f0efb (opens in a new tab)
- https://git.kernel.org/stable/c/9688a46802939da28f00cb40e8129615d5d4af39 (opens in a new tab)
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-76678 (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-89766)Record last updated .