ptp: vmclock: prevent read-only mappings from becoming writable
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 20503272422693d793b84f88bf23fe4e955d3a33 · < a5edadbae57e2298a56cf7a4e774a027905a331f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ptp: vmclock: prevent read-only mappings from becoming writable
vmclock_miscdev_mmap() rejects writable mappings of the shared vmclock ABI page with -EROFS, but leaves VM_MAYWRITE set. Userspace can map the page read-only and then upgrade it to writable with mprotect(), after which the guest can corrupt the host-written timekeeping data (sequence counter, UTC time, TSC offset) that the vmclock ABI defines as read-only.
Clear VM_MAYWRITE on the read-only path so the mapping cannot be upgraded, as i915 does for its read-only objects and as fixed in drm/vc4 (CVE-2026-68445) and drm/panthor (CVE-2024-53071).
From the CVE record · Linux
The Linux kernel's vmclock mapping can be made writable even though it is intended to be read-only. Local userspace can map the shared page read-only, then use mprotect() to make it writable and corrupt host-written timekeeping data.
Engineers running Linux kernels with the vmclock component should check whether their kernel includes this fix; affected versions were not specified.