CVE-2026-99226keys: Avoid the owner account dereference in named keyring lookup
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 92% 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: keys: Avoid the owner account dereference in named keyring lookup Named keyring lookup must keep the storage containing the owner UID alive through the namespace mapping check. find_keyring_by_name() reads keyring->user->uid under keyring_name_lock, but that lock protects the keyring's name entry and allocation, not its separate key_user. A named session-keyring join can overlap a privileged KEYCTL_CHOWN on another CPU. If the keyring holds the last reference to its old dynamic key_user and the ownership transfer succeeds, the following ordering is possible: Named join Chown find_keyring_by_name() keyctl_chown_key() read_lock(keyring_name_lock) down_write(key->sem) load old keyring->user replace key->user and key->uid up_write(key->sem) key_put(key) key_user_put(old user): free read old user->uid read_unlock(keyring_name_lock) Chown neither takes keyring_name_lock nor key_session_mutex, so it can free the old account between the pointer load and the UID read. The lookup then reads freed memory even though the keyring itself is alive. Use keyring->uid for the mapping check. key_alloc() initializes this inline owner UID and keyctl_chown_key() updates it on chown. The existing name lock keeps its containing keyring allocated throughout the check, so lookup no longer depends on the account's lifetime. This also matches the owner UID used by the permission check. KASAN report as below: BUG: KASAN: slab-use-after-free in find_keyring_by_name+0x577/0x5d0 Read of size 4 at addr ffff8881128ae2ec by task keycase/500
Timeline
ID reserved
By Linux
- 38 days later
· 38 days later
Published
- 1 day later
· 1 day 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.18% · top 92% 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 2ea190d0a006ce5218baa6e798512652446a605a – < 77249d4b1bb5ad43552b7023c4a0978937aa7a56
- affected 2ea190d0a006ce5218baa6e798512652446a605a – < 0b865fa477d94ac96c26848aab1fd176397de3f6
- affected 2ea190d0a006ce5218baa6e798512652446a605a – < 6763329f673d261641c79212abf773af77b2c922
- affected 2ea190d0a006ce5218baa6e798512652446a605a – < aa03c8fb4334f14d218020f7431debf2b7766865
- affected 2ea190d0a006ce5218baa6e798512652446a605a – < c9664f780f861dd9f11f120c7a03ed0993671ebb
- affected 2ea190d0a006ce5218baa6e798512652446a605a – < b0830a26e2c3008a6e21863126b4a0e68b2761cd
- affected 2ea190d0a006ce5218baa6e798512652446a605a – < 5c6a9512887a6cc694d594d9c0b57c0841d215b5
- affected 2ea190d0a006ce5218baa6e798512652446a605a – < 40b12b93ae4ab9e22c3d571e9b09fd08afad53f6
- affected 2ea190d0a006ce5218baa6e798512652446a605a – < 51409aaa01f8602552c336009fd22b226b0cdf1d
- affected 2.6.30
- unaffected < 2.6.30
- unaffected 5.10.273 – ≤ 5.10.*
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.161 – ≤ 6.6.*
- unaffected 6.12.115 – ≤ 6.12.*
- unaffected 6.18.60 – ≤ 6.18.*
- unaffected 7.2.14 – ≤ 7.2.*
- unaffected 7.3.1 – ≤ 7.3.*
- unaffected 7.4-rc1 – ≤ *
References
References9
- https://git.kernel.org/stable/c/77249d4b1bb5ad43552b7023c4a0978937aa7a56 (opens in a new tab)
- https://git.kernel.org/stable/c/0b865fa477d94ac96c26848aab1fd176397de3f6 (opens in a new tab)
- https://git.kernel.org/stable/c/6763329f673d261641c79212abf773af77b2c922 (opens in a new tab)
- https://git.kernel.org/stable/c/aa03c8fb4334f14d218020f7431debf2b7766865 (opens in a new tab)
- https://git.kernel.org/stable/c/c9664f780f861dd9f11f120c7a03ed0993671ebb (opens in a new tab)
- https://git.kernel.org/stable/c/b0830a26e2c3008a6e21863126b4a0e68b2761cd (opens in a new tab)
- https://git.kernel.org/stable/c/5c6a9512887a6cc694d594d9c0b57c0841d215b5 (opens in a new tab)
- https://git.kernel.org/stable/c/40b12b93ae4ab9e22c3d571e9b09fd08afad53f6 (opens in a new tab)
- https://git.kernel.org/stable/c/51409aaa01f8602552c336009fd22b226b0cdf1d (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-115268 (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-99226)Record last updated .