cve.bz

CVE-2026-90279 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: md/raid5: round bitmap stripes with sector division raid5_bitmap_sector_map() aligns the array range to full RAID5 stripe widths before converting it to component sectors. That width is chunk_sectors multiplied by the number of data disks, and it is not always a power of two. Reproduce with a 4-disk RAID5, 1024-sector chunks, and three data disks. The full-stripe width is 3072 sectors. For a one-sector write at array sector 3072, correct rounding gives array range [3072, 6144), which maps to component range [1024, 2048). The old round_down()/round_up() logic instead gives [1024, 4096), which maps to [0, 1024). Use sector_div() based arithmetic so the rounded range is aligned to the actual RAID5 stripe width. The deterministic mapper test now reports the fixed component range as [1024, 2048), while the old mask-based range was [0, 1024).
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 promptExplain 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.

ProductAffected
Linuxfrom 6.6.79 before 6.6.157
Linuxfrom 6.12.13 before 6.12.110
Linuxfrom 6.13.2 before 6.14
Linux6.14 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.157
Linux6.126.12.110
Linux6.186.18.52
Linux7.27.2.6
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-90279
Debian13linux6.12.111-1DEBIAN-CVE-2026-90279
Debian14linux7.2.6-1DEBIAN-CVE-2026-90279
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-90279
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-90279
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-90279
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-90279 USN-9024-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-90279 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-90279 USN-9026-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-90279 USN-9024-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-90279 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1069.70~22.04.1UBUNTU-CVE-2026-90279 USN-9024-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-149.149.1~22.04.1UBUNTU-CVE-2026-90279 USN-9024-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-90279 USN-9025-1
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 31 moreno fix listedUBUNTU-CVE-2026-90279
43 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.7-1.1openSUSE-SU-2026:11880-1
Azure Linux3kernel6.6.157.1-1AZL-102824
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-90279
Alpaquitastreamlinux-lts6.18.53-r0BELL-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.

Red Hat's statement

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.

Red Hat's mitigation

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.

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 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtNot affected
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-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-90279.

References

Check your stackJSON