From: patchwork-bot+netdevbpf@kernel.org
To: Abdifatah Suruur <suruurism@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
dwmw2@infradead.org
Subject: Re: [PATCH net] ptp: vmclock: prevent read-only mappings from becoming writable
Date: Tue, 18 Aug 2026 16:50:09 +0000 [thread overview]
Message-ID: <178707180990.2177226.15958799767207354932.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813174707.14809-1-suruurism@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
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
prev parent reply other threads:[~2026-08-18 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 17:47 [PATCH net] ptp: vmclock: prevent read-only mappings from becoming writable Abdifatah Suruur
2026-08-18 16:50 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178707180990.2177226.15958799767207354932.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=suruurism@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.