CVE-2026-90140 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
- EPSS
- 0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th 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.15.221
- Linux Linux: fixed in 6.1.188
- Linux Linux: fixed in 6.6.157
- Linux Linux: fixed in 6.12.110
- Linux Linux: fixed in 6.18.52
- Linux Linux: fixed in 7.2.6
- Linux Linux: fixed in 7.3
- Debian, Ubuntu, openSUSE, Azure Linux, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-90140 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-90140?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-90140?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-90140 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.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | from 5.15.166 before 5.15.221 |
| Linux | from 6.1.107 before 6.1.188 |
| Linux | from 6.6.48 before 6.6.157 |
| Linux | 6.8 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 5.15 | 5.15.221 |
| Linux | 6.1 | 6.1.188 |
| Linux | 6.6 | 6.6.157 |
| Linux | 6.12 | 6.12.110 |
| Linux | 6.18 | 6.18.52 |
| Linux | 7.2 | 7.2.6 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.190-1 | DEBIAN-CVE-2026-90140 |
| Debian | 12 | linux-6.12 | 6.12.111-1~deb12u1 | DEBIAN-CVE-2026-90140 |
| Debian | 13 | linux | 6.12.111-1 | DEBIAN-CVE-2026-90140 |
| Debian | 14 | linux | 7.2.6-1 | DEBIAN-CVE-2026-90140 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-90140 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-90140 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-90140 |
| Ubuntu | 22.04:LTS | linux | 5.15.0-202.212 | UBUNTU-CVE-2026-90140 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-aws | 5.15.0-1119.126 | UBUNTU-CVE-2026-90140 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-90140 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure | 5.15.0-1125.134 | UBUNTU-CVE-2026-90140 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-90140 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde | 5.15.0-1124.133 | UBUNTU-CVE-2026-90140 USN-8962-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-90140 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp | 5.15.0-1120.130 | UBUNTU-CVE-2026-90140 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-90140 USN-9024-1 |
| 77 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| openSUSE | Tumbleweed | kernel-source | 7.2.7-1.1 | openSUSE-SU-2026:11880-1 |
| Azure Linux | 3 | kernel | 6.6.157.1-1 | AZL-102567 |
| Alpaquita | 23 | linux-lts | 6.1.189-r0 | BELL-CVE-2026-90140 |
| Alpaquita | 25 | linux-lts | 6.12.111-r0 | BELL-CVE-2026-90140 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-90140 |
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.
A moderate-impact use-after-free flaw was found in the Linux kernel's cuse (character device in userspace) module. Since commit 053fc4f755ad ("fuse: fix UAF in rcu pathwalks"), fuse_conn_put() releases the fuse_conn asynchronously through call_rcu(), and for cuse the release callback cuse_fc_release() is part of the cuse module itself. If the cuse module is unloaded before the pending RCU callback runs, the callback executes code in module text that has already been freed with vfree(), causing a kernel page fault and system crash; if the freed virtual address is subsequently reused, the stale callback could in specific circumstances execute unrelated code, potentially allowing a local attacker to execute arbitrary code. Red Hat rates this flaw Moderate severity with CVSS 3.1 score 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H): triggering it requires local access with privileges sufficient to load and unload kernel modules plus a race between module unload and the outstanding RCU grace period, so the practical impact is loss of availability rather than reliable code execution. The flaw affects the kernel in Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2, for which the fix is currently deferred; residual risk while the fix is deferred is limited to local privileged users able to unload the cuse module, with a kernel panic being the most likely outcome. Red Hat Enterprise Linux 7, 8, and 9, including the kernel-rt real-time variants, and the RHEL CoreOS kernels shipped with OpenShift Container Platform 4 are not affected because the vulnerable code, introduced with the RCU-delayed fuse_conn release, is not present in those kernels. Upstream fixed the issue by calling rcu_barrier() in cuse_exit() so that any pending fuse_conn release callback completes before the module is removed.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Out of support scope | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Not affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Not affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Not 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-90140.
References
- https://git.kernel.org/stable/c/389bd349ddbcf90dbd8a4f2a4ab6e552d53df134
- https://git.kernel.org/stable/c/45ae914b2f6ea56fc2f1c017fdee4e995bcb4c0e
- https://git.kernel.org/stable/c/4deb3edead0c0e172cc7349e8855d741d3c5e162
- https://git.kernel.org/stable/c/7fe415e1cd8fa875be263670c0ab47109818abb6
- https://git.kernel.org/stable/c/a1b46aee33d83f14ed62d7fdef1a91d3e0b732a9
- https://git.kernel.org/stable/c/ac5c499413385cea3e0220d6050408d50842891d
- https://git.kernel.org/stable/c/c40f3f24839f8404325a2099e26c2a04786ae309