CVSS 3.1
7.0 highCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.0) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-99224 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99224?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99224?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-99224 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 3.18 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 5.10 | 5.10.273 |
| Linux | 5.15 | 5.15.224 |
| Linux | 6.1 | 6.1.191 |
| Linux | 6.6 | 6.6.161 |
| Linux | 6.12 | 6.12.115 |
| Linux | 6.18 | 6.18.60 |
| Linux | 7.2 | 7.2.14 |
| Linux | 7.3 | 7.3.1 |
| Linux | later releases | 7.4-rc1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.192-1 | DEBIAN-CVE-2026-99224 |
| Debian | 12 | linux-6.12 | 6.12.115-2~deb12u1 | DEBIAN-CVE-2026-99224 |
| Debian | 13 | linux | 6.12.115-1 | DEBIAN-CVE-2026-99224 |
| Debian | 14 | linux | 7.2.14-1 | DEBIAN-CVE-2026-99224 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-99224 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-99224 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-99224 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 57 more | no fix listed | UBUNTU-CVE-2026-99224 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 50 more | no fix listed | UBUNTU-CVE-2026-99224 |
| Ubuntu | 26.04:LTS | linux, linux-aws, linux-gcp and 12 more | no fix listed | UBUNTU-CVE-2026-99224 |
| Ubuntu | 26.10 | linux, linux-aws, linux-gcp and 6 more | no fix listed | UBUNTU-CVE-2026-99224 |
| Ubuntu | Nvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTS | linux-bluefield | no fix listed | UBUNTU-CVE-2026-99224 |
| Ubuntu | Pro:14.04:LTS | linux-aws, linux-azure, linux-lts-xenial | no fix listed | UBUNTU-CVE-2026-99224 |
| Ubuntu | Pro:16.04:LTS | linux, linux-aws, linux-gcp and 5 more | no fix listed | UBUNTU-CVE-2026-99224 |
| Ubuntu | Pro:18.04:LTS | linux, linux-aws, linux-kvm and 10 more | no fix listed | UBUNTU-CVE-2026-99224 |
| Ubuntu | Pro:20.04:LTS | linux, linux-aws, linux-gcp and 19 more | no fix listed | UBUNTU-CVE-2026-99224 |
| 4 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| openSUSE | Tumbleweed | kernel-source | 7.3.3-1.1 | openSUSE-SU-2026:12497-1 |
| Azure Linux | 3 | kernel | 6.6.161.1-1 | AZL-112550 |
| Alpaquita | 23 | linux-lts | 6.1.191-r0 | BELL-CVE-2026-99224 |
| Alpaquita | 25 | linux-lts | 6.12.115-r0 | BELL-CVE-2026-99224 |
| Alpaquita | stream | linux-lts | 6.18.62-r0 | BELL-CVE-2026-99224 |
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 rates this Moderate.
Red Hat has evaluated this vulnerability as a Moderate severity impact because triggering the underlying condition requires precise race timing against an administrative kernel module removal, restricting the threat to authenticated local environments. In typical enterprise deployments, kernel modules are loaded at boot or on-demand and rarely unloaded dynamically during routine operations. Furthermore, unprivileged users lack the administrative capabilities necessary to initiate module removal, making deliberate exploitation unlikely under standard operating conditions.
--- CME Mitigation Guidance (2026-11-04) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to block unprivileged invocation of keyctl syscalls via seccomp or disallow runtime unloading of kernel modules that register key types: upgrade to the corresponding fixed Red Hat builds, which hold key->sem for reading across the kasprintf call and release it before copying to userspace, closing race condition between KEYCTL_DESCRIBE and module unloading. Until patched, this is only a concern on Linux systems where local users have View permission on keys backed by dynamically unloadable kernel modules — non-Linux operating systems are unaffected — so prevent routine dynamic unloading of kernel modules and restrict untrusted local user permissions to create or view keys. As a compensating measure, enable runtime memory error detection using KASAN or HWASan to detect use-after-free memory access, enforce SELinux policy to restrict key security classes and deny unauthorized View permissions, map local users to confined SELinux domains lacking permissions to describe kernel keyrings, and deploy gVisor sandboxing to intercept syscalls and isolate the host kernel key subsystem. These controls limit blast radius and contain exploitation, but they do not fix the underlying locking race use-after-free defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-601 Kernel-Level Syscall Filtering (seccomp) (high)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Affected | |
| Red Hat Enterprise Linux 6 | kernel | Affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Affected | |
| Red Hat Enterprise Linux 9 | kernel | Affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-10 | Affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Affected |
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-99224.