Vulnerability · Published Nov 2, 2026 · Assigned by Linux

CVE-2026-99226keys: Avoid the owner account dereference in named keyring lookup

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 8% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 92.1% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-99226
Debian:13linux6.12.115-1DEBIAN-CVE-2026-99226
Debian:14linux7.2.14-1DEBIAN-CVE-2026-99226
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinuxno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.10linuxno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.10linux-awsno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.10linux-azureno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.10linux-gcpno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-hwe-7.0no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-oem-7.0no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.10linux-oracleno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.10linux-raspino fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.10linux-realtimeno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99226
Ubuntu:26.10linux-riscvno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-riscv-7.0no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-99226
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-99226
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-99226

Affected products (as reported)

VendorProductVersions
Linux Linux 2ea190d0a006ce5218baa6e798512652446a605a – before 77249d4b1bb5ad43552b7023c4a0978937aa7a562ea190d0a006ce5218baa6e798512652446a605a – before 0b865fa477d94ac96c26848aab1fd176397de3f62ea190d0a006ce5218baa6e798512652446a605a – before 6763329f673d261641c79212abf773af77b2c9222ea190d0a006ce5218baa6e798512652446a605a – before aa03c8fb4334f14d218020f7431debf2b77668652ea190d0a006ce5218baa6e798512652446a605a – before c9664f780f861dd9f11f120c7a03ed0993671ebb2ea190d0a006ce5218baa6e798512652446a605a – before b0830a26e2c3008a6e21863126b4a0e68b2761cd2ea190d0a006ce5218baa6e798512652446a605a – before 5c6a9512887a6cc694d594d9c0b57c0841d215b52ea190d0a006ce5218baa6e798512652446a605a – before 40b12b93ae4ab9e22c3d571e9b09fd08afad53f6
Linux Linux 2.6.30

References