Linux
ptp: vmclock: prevent read-only mappings from becoming writable
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).
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 20503272422693d793b84f88bf23fe4e955d3a33, < 5b4f2bec7bea6c04084d720d731bedee7caf878d
- >= 20503272422693d793b84f88bf23fe4e955d3a33, < 3f5677d2f817355147337f0453174c7bb0f3b66a
- >= 20503272422693d793b84f88bf23fe4e955d3a33, < 2496e141827102d6af512950057d402a2cfb2bfc
- >= 20503272422693d793b84f88bf23fe4e955d3a33, < 2e596e7814ba38cdc129991058b6c254ed37cb11
- >= 20503272422693d793b84f88bf23fe4e955d3a33, < 0ce59c4148ecd1520c5592a63bb3c8991ee2d326
- >= 20503272422693d793b84f88bf23fe4e955d3a33, < a5edadbae57e2298a56cf7a4e774a027905a331f
Fixed in 5b4f2bec7bea6c04084d720d731bedee7caf878d, 3f5677d2f817355147337f0453174c7bb0f3b66a, 2496e141827102d6af512950057d402a2cfb2bfc, 2e596e7814ba38cdc129991058b6c254ed37cb11, 0ce59c4148ecd1520c5592a63bb3c8991ee2d326, a5edadbae57e2298a56cf7a4e774a027905a331f
- 6.13
Fixed in 0, 6.18.47, 6.18.50, 7.1.11, 7.2.1, 7.2.4, 7.3
Mitigation
Upgrade Linux to 5b4f2bec7bea6c04084d720d731bedee7caf878d or 3f5677d2f817355147337f0453174c7bb0f3b66a or 2496e141827102d6af512950057d402a2cfb2bfc or 2e596e7814ba38cdc129991058b6c254ed37cb11 or 0ce59c4148ecd1520c5592a63bb3c8991ee2d326 or a5edadbae57e2298a56cf7a4e774a027905a331f or later.
Upgrade Linux to 0 or 6.18.47 or 6.18.50 or 7.1.11 or 7.2.1 or 7.2.4 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 informational
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| suruurism/cve-writeups-and-pocs | 30 Aug 2026 +2.4 d | 1 | Informational · list
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.