From: phind.uet@gmail.com
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Nguyen Dinh Phi <phind.uet@gmail.com>,
syzbot+cde12433b6c56f55d9ed@syzkaller.appspotmail.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] KVM: pfncache: Fix uhva validity check in kvm_gpc_is_valid_len()
Date: Mon, 9 Mar 2026 15:56:29 +0800 [thread overview]
Message-ID: <20260309075629.24569-2-phind.uet@gmail.com> (raw)
From: Nguyen Dinh Phi <phind.uet@gmail.com>
In kvm_gpc_is_valid_len(), if the GPA is an error GPA, the function uses
uhva to calculate the page offset. However, if uhva is invalid, its value
can still be page-aligned (for example, PAGE_OFFSET) and this function will
still return true.
An invalid uhva could lead to incorrect offset calculations and potentially
trigger a WARN_ON_ONCE in __kvm_gpc_refresh().
Fixing it by adding an additional check for uhva.
Signed-off-by: Nguyen Dinh Phi <phind.uet@gmail.com>
Reported-by: syzbot+cde12433b6c56f55d9ed@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=cde12433b6c56f55d9ed
---
virt/kvm/pfncache.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/virt/kvm/pfncache.c b/virt/kvm/pfncache.c
index 728d2c1b488a..707ead0a096c 100644
--- a/virt/kvm/pfncache.c
+++ b/virt/kvm/pfncache.c
@@ -60,8 +60,16 @@ void gfn_to_pfn_cache_invalidate_start(struct kvm *kvm, unsigned long start,
static bool kvm_gpc_is_valid_len(gpa_t gpa, unsigned long uhva,
unsigned long len)
{
- unsigned long offset = kvm_is_error_gpa(gpa) ? offset_in_page(uhva) :
- offset_in_page(gpa);
+ unsigned long offset;
+
+ if (kvm_is_error_gpa(gpa)) {
+ if (kvm_is_error_hva(uhva))
+ return false;
+
+ offset = offset_in_page(uhva);
+ } else {
+ offset = offset_in_page(gpa);
+ }
/*
* The cached access must fit within a single page. The 'len' argument
--
2.43.0
next reply other threads:[~2026-03-09 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 7:56 phind.uet [this message]
2026-03-09 14:39 ` [PATCH] KVM: pfncache: Fix uhva validity check in kvm_gpc_is_valid_len() Sean Christopherson
2026-03-09 16:02 ` Phi Nguyen
2026-03-09 19:39 ` Sean Christopherson
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=20260309075629.24569-2-phind.uet@gmail.com \
--to=phind.uet@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=syzbot+cde12433b6c56f55d9ed@syzkaller.appspotmail.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