cve.bz

CVE-2026-99225 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: keys: Check the authorization payload in process keyring searches An authorization payload and its saved credentials must remain valid while search_process_keyrings_rcu() searches the requestor's keyrings. The function validates the authorization key, then separately loads payload.data[0] and unconditionally reads rka->cred. Validation does not prevent request_key_auth_revoke() from clearing the payload. A request-key helper can assume authority and fork a descendant that inherits the authorization key. If the descendant misses in its own keyrings, it falls back to the saved requestor credentials. Successful target instantiation invalidates the authorization key without clearing the payload. After the helper exits, UMH_WAIT_PROC returns to the requester, which calls complete_request_key() and revokes that key. With the descendant paused after validation, the paths can interleave as follows: 1. The descendant enters search_process_keyrings_rcu() under RCU and key_validate() succeeds. 2. The helper instantiates the target, invalidates the authorization key, and exits. 3. The requester resumes from UMH_WAIT_PROC, calls complete_request_key(), and revokes the authorization key. request_key_auth_revoke() sets its payload pointer to NULL. 4. The descendant loads NULL and dereferences rka->cred. This NULL dereference can oops the kernel. RCU delays payload disposal but does not prevent the pointer from being cleared. Load the payload with dereference_key_rcu() and require a non-NULL result before validating the authorization key and searching its saved credentials. A non-NULL payload and its credentials remain alive for the caller's RCU read-side section; a cleared payload skips the fallback search and follows the existing error selection. KASAN report as below: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] RIP: 0010:search_process_keyrings_rcu+0x32b/0x790
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.273
  • Linux Linux: fixed in 5.15.224
  • Linux Linux: fixed in 6.1.191
  • Linux Linux: fixed in 6.6.161
  • Linux Linux: fixed in 6.12.115
  • Linux Linux: fixed in 6.18.60
  • Linux Linux: fixed in 7.2.14
  • Linux Linux: fixed in 7.3.1
  • Debian, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-99225 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99225?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99225?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99225 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-99225

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-99225](https://cve.bz/cve/badge/CVE-2026-99225.svg)](https://cve.bz/cve/CVE-2026-99225)

HTML:

<a href="https://cve.bz/cve/CVE-2026-99225"><img src="https://cve.bz/cve/badge/CVE-2026-99225.svg" alt="CVE-2026-99225"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.3 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.273
Linux5.155.15.224
Linux6.16.1.191
Linux6.66.6.161
Linux6.126.12.115
Linux6.186.18.60
Linux7.27.2.14
Linux7.37.3.1
Linuxlater releases7.4-rc1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-99225
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-99225
Debian13linux6.12.115-1DEBIAN-CVE-2026-99225
Debian14linux7.2.14-1DEBIAN-CVE-2026-99225
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-99225
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-99225
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-99225
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 57 moreno fix listedUBUNTU-CVE-2026-99225
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 50 moreno fix listedUBUNTU-CVE-2026-99225
Ubuntu26.04:LTSlinux, linux-aws, linux-gcp and 12 moreno fix listedUBUNTU-CVE-2026-99225
Ubuntu26.10linux, linux-aws, linux-gcp and 6 moreno fix listedUBUNTU-CVE-2026-99225
UbuntuNvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2026-99225
UbuntuPro:18.04:LTSlinux-aws-5.4, linux-gcp-5.4, linux-hwe-5.4 and 4 moreno fix listedUBUNTU-CVE-2026-99225
UbuntuPro:20.04:LTSlinux, linux-aws, linux-gcp and 19 moreno fix listedUBUNTU-CVE-2026-99225
UbuntuPro:FIPS-preview:22.04:LTS, Pro:FIPS-updates:20.04:LTS, Pro:FIPS-updates:22.04:LTS and 2 morelinux-fips, linux-aws-fips, linux-gcp-fips and 1 moreno fix listedUBUNTU-CVE-2026-99225
UbuntuPro:Realtime:22.04:LTSlinux-realtime, linux-realtime-6.8, linux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-99225
1 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.3.3-1.1openSUSE-SU-2026:12497-1
Azure Linux3kernel6.6.161.1-1AZL-112553
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-99225
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-99225
Alpaquitastreamlinux-lts6.18.62-r0BELL-CVE-2026-99225

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because exploitation is confined to local authenticated users and requires winning a tightly timed race condition. An unprivileged local user could leverage this timing window during process keyring lookups to trigger a kernel panic, resulting in a denial of service. The flaw affects system availability exclusively and does not allow privilege escalation or unauthorized data disclosure.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-10Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-99225.

References

Check your stackJSON