cve.bz

CVE-2026-89718 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: zram: fix out-of-bounds access in writeback_store() Patch series "zram: fix stale scan bounds after reinitialization". Both writeback_store() and read_block_state() derive their table scan bounds from zram->disksize before acquiring dev_lock. If the device is reset and reinitialized with a smaller disksize between that read and lock acquisition, the bound can describe the old table while the scan operates on the new one. This can lead to out-of-bounds slot accesses. Move both bound calculations under dev_lock so each bound remains consistent with the table throughout its scan. Keep the fixes separate because the affected interfaces originate from different commits and can be backported independently. This patch (of 2): writeback_store() calculates the table scan bounds before taking dev_lock. A reset followed by reconfiguration with a smaller disksize can therefore replace zram->table while writeback_store() is waiting for the lock. Once it acquires the lock, it sees an initialized device but scans the new table using the old upper bound, resulting in an out-of-bounds access. Calculate the number of pages while holding dev_lock so the scan bound matches the table protected by the lock.
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; 7th 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.1.191
  • Linux Linux: fixed in 6.6.160
  • Linux Linux: fixed in 6.12.111
  • Linux Linux: fixed in 6.18.57
  • Linux Linux: fixed in 7.2.4
  • 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-89718 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89718?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89718?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-89718 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
Linux5.0 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.191
Linux6.66.6.160
Linux6.126.12.111
Linux6.186.18.57
Linux7.27.2.4
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-89718
Debian12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-89718
Debian13linux6.12.111-1DEBIAN-CVE-2026-89718
Debian14linux7.2.6-1DEBIAN-CVE-2026-89718
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-89718
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-89718
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-89718
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 48 moreno fix listedUBUNTU-CVE-2026-89718
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-89718 USN-9024-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-89718 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-89718 USN-9026-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-89718 USN-9024-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-89718 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1069.70~22.04.1UBUNTU-CVE-2026-89718 USN-9024-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-149.149.1~22.04.1UBUNTU-CVE-2026-89718 USN-9024-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-89718 USN-9025-1
48 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.7-1.1openSUSE-SU-2026:11880-1
Azure Linux3kernel6.6.161.1-1AZL-100151
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-89718
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-89718
Alpaquitastreamlinux-lts6.18.58-r0BELL-CVE-2026-89718

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 flaw was found in the Linux kernel's zram compressed block device driver. The writeback_store() function computes its table scan bounds from zram->disksize before acquiring the device lock (dev_lock), so if the zram device is reset and reinitialized with a smaller disksize while writeback_store() waits for the lock, it scans the new, smaller table using the stale, larger bound, resulting in an out-of-bounds access to kernel memory. A local attacker with access to the zram control interfaces who can reset and reconfigure a zram device while writeback is triggered could exploit this race condition to crash the kernel, causing a denial of service; confidentiality and integrity are not directly impacted (Red Hat CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). The kernel and kernel-rt packages in Red Hat Enterprise Linux 9 and 10, Red Hat In-Vehicle OS 2, and OpenShift Container Platform releases that ship the RHEL 9-based Red Hat Enterprise Linux CoreOS kernel (4.13 and later) are affected. Because this flaw is rated moderate severity with a CVSS score below the threshold used to file fixes, the fix is deferred and no updated packages are currently planned, leaving a residual risk of local denial of service through a kernel crash on affected systems. Red Hat Enterprise Linux 6, 7, and 8 (including kernel-rt) and OpenShift Container Platform 4.12, which ships the RHEL 8-based CoreOS kernel, are not affected because the vulnerable code is not present in those kernels.

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

References

Check your stackJSON