cve.bz

CVE-2026-89793 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. 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: ublk: clear VM_MAYWRITE on read-only ublk char device mmap ublk_ch_mmap() rejects mmap requests with VM_WRITE set, but never clears VM_MAYWRITE on the resulting read-only mapping. This allows a userspace daemon to mmap the per-queue command buffer PROT_READ, then upgrade it to PROT_WRITE via mprotect(), since VM_MAYWRITE was never cleared. The command buffer holds struct ublksrv_io_desc entries that are kernel-written ABI; a writable mapping lets an unprivileged daemon process corrupt fields such as addr, op_flags, nr_sectors, and start_sector. Same bug class as the drm/panthor and drm/vc4 VM_MAYWRITE fixes, and the 2026-08-13 ptp/vmclock fix (a5edadbae57e). Verified via mprotect() PoC: before the fix, a PROT_READ mapping can be upgraded to PROT_READ|PROT_WRITE and a write into the command buffer corrupts io_desc fields (confirmed under KASAN). After the fix, mprotect() returns -EACCES.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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; 6th 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.51
  • Linux Linux: fixed in 7.2.5
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, openSUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

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

Fixed in

ProductRelease lineFixed in
Linux6.66.6.157
Linux6.126.12.110
Linux6.186.18.51
Linux7.27.2.5
Linuxlater releases7.3

Linux distributions

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

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 protection flaw in ublk_ch_mmap leaves VM_MAYWRITE set on a command buffer that is intended to be mapped read only. A local ublk daemon can map the buffer with PROT_READ and then use mprotect to upgrade the mapping to PROT_WRITE, gaining a constrained write primitive over kernel-written ublksrv_io_desc entries. The attacker can modify fields such as addr, op_flags, nr_sectors, and start_sector while the buffer participates in block I/O processing. This can corrupt request semantics, disrupt the affected ublk device, damage data, or cause a denial of service. A direct arbitrary kernel write or reliable privilege escalation is not established, but the writable kernel-allocated ABI buffer creates a plausible memory corruption boundary that requires review of all later kernel consumers. For the CVSS the PR:L is selected because triggering requires a local process with access to the affected ublk character device, but it does not necessarily require full root privileges. The issue is not directly network reachable. The paranoid score uses CIA:HHH because controlled corruption of kernel-owned I/O descriptors may have broader confidentiality, integrity, and availability consequences if any later kernel path trusts the modified fields.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't 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 10kernelAffected
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-9Not affected

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-89793.

References

Check your stackJSON