CVE-2026-89772 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 7.2.4
- Linux Linux: fixed in 7.3
- Debian, openSUSE: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-89772 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89772?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89772?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-89772 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 | 6.13 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 7.2 | 7.2.4 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.2.6-1 | DEBIAN-CVE-2026-89772 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-89772 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-89772 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-89772 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-89772 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-aws-7.0, linux-gcp-7.0 and 33 more | no fix listed | UBUNTU-CVE-2026-89772 |
| Ubuntu | 26.04:LTS | linux, linux-aws, linux-gcp and 12 more | no fix listed | UBUNTU-CVE-2026-89772 |
| Ubuntu | Pro:Realtime:24.04:LTS | linux-realtime-6.14, linux-realtime-6.17 | no fix listed | UBUNTU-CVE-2026-89772 |
| openSUSE | Tumbleweed | kernel-source | 7.2.7-1.1 | openSUSE-SU-2026:11880-1 |
| Alpaquita | stream | linux-lts | no fix listed | BELL-CVE-2026-89772 |
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; 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 flaw was found in the Btrfs filesystem of the Linux kernel, rated moderate impact by Red Hat. Changes introduced in the upstream 6.13 kernel development cycle removed an early folio_clear_dirty_for_io() call during data writeback, which also dropped the folio_mkclean() call that write-protects shared memory-mapped page table entries. As a result, a local process that has a file memory-mapped with write access can modify a folio while the kernel is checksumming, compressing, copying, or writing it back, without triggering a page fault. This race condition can lead to data corruption (invalid checksums and corruption reports on subsequent reads) or to silent data loss, where writes present in the page cache are discarded when the folio's dirty bit is cleared, even if fsync() was called. The issue also affects zoned submissions, inline extents, folios spanning EOF, and compressed extents. Red Hat Enterprise Linux 7, 8, 9, and 10 are not affected because the vulnerable code, introduced upstream in the 6.13 kernel, is not present in the shipped Red Hat kernel versions, and OpenShift Container Platform 4 RHEL CoreOS builds that use those kernels are likewise not affected. OpenShift Container Platform 5.0 and 5.1 are affected; the fix is currently deferred for these streams and will be delivered through a future RHEL CoreOS kernel update. Until the fix is delivered, the residual risk remains that a local user with write access to a memory-mapped file on a Btrfs filesystem could trigger data corruption or data loss.
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 | Not affected | |
| 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 | 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-89772.