From: patchwork-bot+linux-riscv@kernel.org
To: eanut 6 <jiakaipeanut@gmail.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kvm-riscv@lists.infradead.org, kvm@vger.kernel.org,
anup@brainfault.org, atish.patra@linux.dev, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
xujiakai2025@iscas.ac.cn, jiakaiPeanut@gmail.com
Subject: Re: [PATCH] RISC-V: KVM: Fix null pointer dereference in kvm_riscv_aia_imsic_rw_attr()
Date: Fri, 20 Feb 2026 04:11:05 +0000 [thread overview]
Message-ID: <177156066578.189817.1206944543601300200.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260127072219.3366607-1-xujiakai2025@iscas.ac.cn>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Anup Patel <anup@brainfault.org>:
On Tue, 27 Jan 2026 07:22:19 +0000 you wrote:
> Add a null pointer check for imsic_state before dereferencing it in
> kvm_riscv_aia_imsic_rw_attr(). While the function checks that the
> vcpu exists, it doesn't verify that the vcpu's imsic_state has been
> initialized, leading to a null pointer dereference when accessed.
>
> The crash manifests as:
> Unable to handle kernel paging request at virtual address
> dfffffff00000006
> ...
> kvm_riscv_aia_imsic_rw_attr+0x2d8/0x854 arch/riscv/kvm/aia_imsic.c:958
> aia_set_attr+0x2ee/0x1726 arch/riscv/kvm/aia_device.c:354
> kvm_device_ioctl_attr virt/kvm/kvm_main.c:4744 [inline]
> kvm_device_ioctl+0x296/0x374 virt/kvm/kvm_main.c:4761
> vfs_ioctl fs/ioctl.c:51 [inline]
> ...
>
> [...]
Here is the summary with links:
- RISC-V: KVM: Fix null pointer dereference in kvm_riscv_aia_imsic_rw_attr()
https://git.kernel.org/riscv/c/aeb1d17d1af5
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-02-20 4:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 7:22 Jiakai Xu
2026-01-28 15:08 ` Anup Patel
2026-02-20 4:11 ` patchwork-bot+linux-riscv [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=177156066578.189817.1206944543601300200.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=jiakaipeanut@gmail.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=xujiakai2025@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®