CVE-2026-90279 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; 10th 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 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-90279 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-90279?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-90279?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-90279 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 6.6.79 before 6.6.157 |
| Linux | from 6.12.13 before 6.12.110 |
| Linux | from 6.13.2 before 6.14 |
| Linux | 6.14 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| 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.12 | 6.12.111-1~deb12u1 | DEBIAN-CVE-2026-90279 |
| Debian | 13 | linux | 6.12.111-1 | DEBIAN-CVE-2026-90279 |
| Debian | 14 | linux | 7.2.6-1 | DEBIAN-CVE-2026-90279 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-90279 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-90279 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-90279 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-90279 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-90279 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-90279 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-90279 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-hwe-6.8 | 6.8.0-149.149~22.04.1 | UBUNTU-CVE-2026-90279 USN-9066-1 |
| Ubuntu | 22.04:LTS | linux-ibm-6.8 | 6.8.0-1069.70~22.04.1 | UBUNTU-CVE-2026-90279 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-149.149.1~22.04.1 | UBUNTU-CVE-2026-90279 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-oracle-6.8 | 6.8.0-1067.71~22.04.1 | UBUNTU-CVE-2026-90279 USN-9025-1 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 31 more | no fix listed | UBUNTU-CVE-2026-90279 |
| 43 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-102824 |
| Alpaquita | 25 | linux-lts | 6.12.111-r0 | BELL-CVE-2026-90279 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-90279 |
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 severity flaw was found in the Linux kernel's md/raid5 driver. The raid5_bitmap_sector_map() function aligned array sector ranges to full RAID5 stripe widths using mask-based round_down()/round_up() arithmetic before converting them to component sectors. Because the full stripe width, computed as the chunk size multiplied by the number of data disks, is not always a power of two, this rounding is incorrect on such geometries and the wrong component sector range can be recorded in the RAID5 write-intent bitmap for write operations (for example, a one-sector write on an array whose full-stripe width is 3072 sectors). Triggering this requires local access with write privileges to an already-configured RAID5 array whose full stripe width is not a power of two, and the consequence can be data corruption or unintended data access within the array, affecting the correctness of subsequent recovery or rebuild operations. Red Hat assessed the impact as Moderate (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
The vulnerable raid5 bitmap sector-mapping code is present only in later kernel streams. Red Hat Enterprise Linux 7, the RHEL 8.4, 8.6, and 8.8 streams, the RHEL 9.2, 9.4, and 9.6 streams, the RHEL 10.0 stream, and OpenShift Container Platform 4.12 through 4.21 are not affected because the vulnerable code is not present there. The kernel package (and the kernel-rt variant in RHEL 8.10) in Red Hat Enterprise Linux 8.10, the RHEL 9.8, 9.9, and 9.10 streams, and the RHEL 10.2, 10.3, and 10.4 streams, as well as Red Hat In-Vehicle OS 2 and OpenShift Container Platform 4.22, 4.23, 5.0, and 5.1 via RHEL CoreOS 9, are affected, and the fix is currently deferred. Because the flaw is rated Moderate and is reachable only through local write access to a RAID5 array with a specific geometry, an immediate update is not planned; the residual risk until a fix ships is that writes on affected arrays may track incorrect bitmap component ranges, which can compromise data integrity and recovery correctness on those arrays.
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 | Fix deferred | |
| Red Hat Enterprise Linux 8 | kernel-rt | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| 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 | Fix deferred | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Fix 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-90279.
References
- https://git.kernel.org/stable/c/02c10581866d08822c6348e299881485fc546185
- https://git.kernel.org/stable/c/17ea021ae74987d6064c8195c4922fa025753892
- https://git.kernel.org/stable/c/9d7490007707f90691911385365bd1d691d99225
- https://git.kernel.org/stable/c/cab7d949b18b2f1cd625689dc16c5f81236bac93
- https://git.kernel.org/stable/c/ccbdc483eb041eef809e9ff223d1ad63518a2c52