Linux vulnerability

What happened

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.

Affected versions

Linux: 71f28f3136aff5890cd56de78abc673f8393cad9 through before be41733c24be58e2a1ef718c80fafdfb98a40d5e (git); 71f28f3136aff5890cd56de78abc673f8393cad9 through before 5befd06a72216869b607cf7724a4f16c6a2d3999 (git); 71f28f3136aff5890cd56de78abc673f8393cad9 through before e373c1acdbcf88cec533ece9f589020adaed0a78 (git); 71f28f3136aff5890cd56de78abc673f8393cad9 through before fa5e1bc673ca59722608af67b27e65dba0c97926 (git); 71f28f3136aff5890cd56de78abc673f8393cad9 through before 6e2b571b0a54755b06e092501913e1dfefe75d6c (git); 6.0 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

• Apply vendor-provided updates or mitigations.
• Review affected product exposure and access logs.