Re: [PATCH net] ptp: vmclock: prevent read-only mappings from becoming writable
| Newsgroups | org.kernel.vger.linux-kernel,org.kernel.vger.netdev |
|---|---|
| Message-ID | <178707180990.2177226.15958799767207354932.git-patchwork-notify@kernel.org> |
Hello: This patch was applied to netdev/net.git (main) by Jakub Kicinski <[email protected]>: On Thu, 13 Aug 2026 20:47:07 +0300 you wrote: > 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). > > [...] Here is the summary with links: - [net] ptp: vmclock: prevent read-only mappings from becoming writable https://git.kernel.org/netdev/net/c/a5edadbae57e You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html