From: zhenwei pi <pizhenwei@bytedance.com>
To: mst@redhat.com, arei.gonglei@huawei.com
Cc: qemu-devel@nongnu.org, taoym@zju.edu.cn, kangel@zju.edu.cn,
nop.leixiao@gmail.com, mcascell@redhat.com,
zhenwei pi <pizhenwei@bytedance.com>
Subject: [PATCH 0/2] CEV fixes for virtio-crypto
Date: Thu, 3 Aug 2023 10:43:12 +0800 [thread overview]
Message-ID: <20230803024314.29962-1-pizhenwei@bytedance.com> (raw)
Hi Michael, Lei,
Yiming Tao, Yongkang Jia, Xiao Lei(from Zhejiang University) reported
issuses and CVEs in the past days.
This series fixes a CVE and a BUG for virtio-crypto/cryptodev.
Zhenwei Pi (2):
virtio-crypto: verify src&dst buffer length for sym request
cryptodev: Handle unexpected request to avoid crash
backends/cryptodev.c | 10 ++++++++++
hw/virtio/virtio-crypto.c | 5 +++++
2 files changed, 15 insertions(+)
--
2.34.1
next reply other threads:[~2023-08-03 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 2:43 zhenwei pi [this message]
2023-08-03 2:43 ` [PATCH 1/2] virtio-crypto: verify src&dst buffer length for sym request zhenwei pi
2023-08-03 2:43 ` [PATCH 2/2] cryptodev: Handle unexpected request to avoid crash zhenwei pi
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=20230803024314.29962-1-pizhenwei@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=arei.gonglei@huawei.com \
--cc=kangel@zju.edu.cn \
--cc=mcascell@redhat.com \
--cc=mst@redhat.com \
--cc=nop.leixiao@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=taoym@zju.edu.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;
as well as URLs for NNTP newsgroup(s).