From: patchwork-bot+netdevbpf@kernel.org
To: Yuho Choi <oss.patchbox@gmail.com>
Cc: richardcochran@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, jpiotrowski@linux.microsoft.com,
netdev@vger.kernel.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v1] ptp: kvm: x86: Leak clock_pair page if changing its encryption fails
Date: Tue, 10 Nov 2026 23:20:06 +0000 [thread overview]
Message-ID: <179435280642.110597.5760305396342479169.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261105164324.23501-2-oss.patchbox@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 5 Nov 2026 11:43:08 -0500 you wrote:
> In a confidential guest, kvm_arch_ptp_init() shares the clock_pair page
> with the host using set_memory_decrypted(), and kvm_arch_ptp_exit()
> makes it private again with set_memory_encrypted() before freeing it.
>
> The untrusted host can make either call fail and leave the page shared.
> Both paths still free the page: the init error path with __free_page(),
> and kvm_arch_ptp_exit() after only a WARN_ON(). The page allocator can
> then hand a page the host can still access to an unrelated user.
>
> [...]
Here is the summary with links:
- [net-next,v1] ptp: kvm: x86: Leak clock_pair page if changing its encryption fails
https://git.kernel.org/netdev/net/c/6a01fb125ba6
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-11-10 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 16:43 [PATCH net-next v1] ptp: kvm: x86: Leak clock_pair page if changing its encryption fails Yuho Choi
2026-11-10 23:20 ` 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=179435280642.110597.5760305396342479169.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=jpiotrowski@linux.microsoft.com \
--cc=kuba@kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss.patchbox@gmail.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox