← All Advisories

CVE-2026-89793

Last refreshed2026-10-05

Status: UPDATED  |  Advisory ID: CVE-2026-89793

Key Details

CVECVE-2026-89793
CVSS Score / Version7.8 (High) / CVSS v3.1
Updated2026-10-05
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Proseattack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected productsLinux Linux

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux
SubsystemsGeneral OT
SectorsMultiple

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-89793
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-89793