cve.bz

CVE-2026-89502 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: ring-buffer: Free cpu_buffer::free_page with subbuf_order When sub-buffers use an order greater than 0, cpu_buffer->free_page is allocated with subbuf_order. Use the correct order for cpu_buffer->free_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 6.12.109
  • Linux Linux: fixed in 6.18.50
  • Linux Linux: fixed in 7.2.4
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, SUSE, openSUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-89502 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89502?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89502?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-89502 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
Linux6.8 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.109
Linux6.186.18.50
Linux7.27.2.4
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-89502
Debian13linux6.12.111-1DEBIAN-CVE-2026-89502
Debian14linux7.2.6-1DEBIAN-CVE-2026-89502
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-89502
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-89502
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-89502
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-89502 USN-9024-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-89502 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-89502 USN-9026-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-89502 USN-9024-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-89502 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1069.70~22.04.1UBUNTU-CVE-2026-89502 USN-9024-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-149.149.1~22.04.1UBUNTU-CVE-2026-89502 USN-9024-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-89502 USN-9025-1
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 31 moreno fix listedUBUNTU-CVE-2026-89502
43 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.39.1SUSE-SU-2026:24197-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.39.1SUSE-SU-2026:24235-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.39.1.160000.2.26SUSE-SU-2026:24235-1
SUSELinux Enterprise Server for NVIDIA 16.1kernel-nvidia64kb, kernel-source-nvidia6.12.0-160100.6.1SUSE-SU-2026:24691-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.39.1.160000.2.26SUSE-SU-2026:24184-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.39.1SUSE-SU-2026:24184-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.39.1SUSE-SU-2026:24179-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.39.1.160000.2.25openSUSE-SU-2026:22091-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.39.1openSUSE-SU-2026:22091-1
openSUSELeap 16.1kernel-default-base6.12.0-160100.9.1.160100.3.14openSUSE-SU-2026:22309-1
openSUSELeap 16.1kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia6.12.0-160100.6.1openSUSE-SU-2026:22313-1
openSUSELeap 16.1kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160100.9.1openSUSE-SU-2026:22309-1
openSUSETumbleweedkernel-source7.2.6-1.1openSUSE-SU-2026:11805-1
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-89502
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-89502

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 · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low impact flaw was found in the Linux kernel's tracing ring-buffer implementation. When a ring buffer is configured with sub-buffers using a memory allocation order greater than 0, the per-CPU spare page (cpu_buffer->free_page) is freed using an incorrect order, causing incorrect memory deallocation and potential kernel memory corruption. Exploitation requires local access to a system whose tracing ring buffer uses such a configuration. Red Hat's assessment rates the consequences as availability only (CVSS:3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H): the practical impact is a system crash (denial of service). Although the upstream description notes that memory corruption could in principle allow privilege escalation, no such path is established by the current evidence.

Red Hat Enterprise Linux 6, 7, 8, and 9 (kernel and kernel-rt) are not affected because the vulnerable code is not present in those kernels, and OpenShift Container Platform 4 versions (RHEL CoreOS) are not affected for the same reason; the affected code was introduced upstream in kernel version 6.8. The currently affected Red Hat offerings include OpenShift Container Platform 5.0 and 5.1, for which the fix is deferred. The deferral reflects the low impact of this flaw: it requires local access, is confined to the tracing ring-buffer free path, and only manifests when larger sub-buffer orders are configured. The residual risk on such systems is kernel memory corruption leading to a system crash, with no direct confidentiality or integrity impact.

Red Hat's mitigation

This issue only manifests when the kernel tracing ring buffer is configured with sub-buffer memory allocation orders greater than 0. Configuring tracing ring buffers to use order-0 sub-buffers avoids triggering the incorrect free. For the affected Red Hat offerings the fix is currently deferred; affected kernels should be updated once a fixed kernel is released for the corresponding update stream. Upstream, this issue is resolved in current stable kernel releases.

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 9kernelNot affected
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-9Not affected
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-89502.

References

Check your stackJSON