From: Oliver Upton <oliver.upton@linux.dev>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>,
kvm@vger.kernel.org, kvmarm@lists.linux.dev,
Zenghui Yu <yuzenghui@huawei.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Dmitry Vyukov <dvyukov@google.com>,
James Morse <james.morse@arm.com>,
Alexander Potapenko <glider@google.com>
Subject: [GIT PULL] KVM/arm64 fixes for 6.9, part #2
Date: Wed, 24 Apr 2024 12:39:46 -0700 [thread overview]
Message-ID: <ZilgAmeusaMd_UeZ@linux.dev> (raw)
Hi Paolo,
Single fix this time around for a rather straightforward NULL
dereference in one of the vgic ioctls, along with a reproducer I've
added as a testcase in selftests.
Please pull.
--
Thanks,
Oliver
The following changes since commit fec50db7033ea478773b159e0e2efb135270e3b7:
Linux 6.9-rc3 (2024-04-07 13:22:46 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-6.9-2
for you to fetch changes up to 160933e330f4c5a13931d725a4d952a4b9aefa71:
KVM: selftests: Add test for uaccesses to non-existent vgic-v2 CPUIF (2024-04-24 19:09:36 +0000)
----------------------------------------------------------------
KVM/arm64 fixes for 6.9, part #2
- Fix + test for a NULL dereference resulting from unsanitised user
input in the vgic-v2 device attribute accessors
----------------------------------------------------------------
Oliver Upton (2):
KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr()
KVM: selftests: Add test for uaccesses to non-existent vgic-v2 CPUIF
arch/arm64/kvm/vgic/vgic-kvm-device.c | 8 ++--
tools/testing/selftests/kvm/aarch64/vgic_init.c | 49 +++++++++++++++++++++++++
2 files changed, 53 insertions(+), 4 deletions(-)
next reply other threads:[~2024-04-24 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 19:39 Oliver Upton [this message]
2024-04-30 8:16 ` [GIT PULL] KVM/arm64 fixes for 6.9, part #2 Oliver Upton
2024-04-30 8:28 ` Paolo Bonzini
2024-04-30 8:29 ` Oliver Upton
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=ZilgAmeusaMd_UeZ@linux.dev \
--to=oliver.upton@linux.dev \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).