patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: stable@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-stable] [PATCH v20.02 0/6] Fix vhost security issues
Date: Mon, 18 May 2020 14:17:59 +0100	[thread overview]
Message-ID: <20200518131805.716052-1-ferruh.yigit@intel.com> (raw)

From: Maxime Coquelin <maxime.coquelin@redhat.com>

Marvin Liu (1):
  vhost: fix translated address not checked

Maxime Coquelin (3):
  vhost: check log mmap offset and size overflow
  vhost: fix vring index check
  vhost/crypto: validate keys lengths

Xiaolong Ye (1):
  vhost: fix potential memory space leak

Xuan Ding (1):
  vhost: fix potential fd leak

 lib/librte_vhost/vhost_crypto.c | 17 +++++++++++++++++
 lib/librte_vhost/vhost_user.c   | 30 +++++++++++++++++++++++-------
 lib/librte_vhost/virtio_net.c   |  4 ++++
 3 files changed, 44 insertions(+), 7 deletions(-)

-- 
2.25.2


             reply	other threads:[~2020-05-18 13:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 13:17 Ferruh Yigit [this message]
2020-05-18 13:18 ` [dpdk-stable] [PATCH v20.02 1/6] vhost: check log mmap offset and size overflow Ferruh Yigit
2020-05-18 13:18 ` [dpdk-stable] [PATCH v20.02 2/6] vhost: fix vring index check Ferruh Yigit
2020-05-18 13:18 ` [dpdk-stable] [PATCH v20.02 3/6] vhost/crypto: validate keys lengths Ferruh Yigit
2020-05-18 13:18 ` [dpdk-stable] [PATCH v20.02 4/6] vhost: fix translated address not checked Ferruh Yigit
2020-05-18 13:18 ` [dpdk-stable] [PATCH v20.02 5/6] vhost: fix potential memory space leak Ferruh Yigit
2020-05-18 13:18 ` [dpdk-stable] [PATCH v20.02 6/6] vhost: fix potential fd leak Ferruh Yigit

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=20200518131805.716052-1-ferruh.yigit@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=stable@dpdk.org \
    /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).