From: Olivier Matz <olivier.matz@6wind.com>
To: Xiaolong Ye <xiaolong.ye@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2] mbuf: fix out-of-bounds access
Date: Thu, 11 Jun 2020 17:03:36 +0200 [thread overview]
Message-ID: <20200611150336.GB12564@platinum> (raw)
In-Reply-To: <20200611004801.105736-1-xiaolong.ye@intel.com>
On Thu, Jun 11, 2020 at 08:48:01AM +0800, Xiaolong Ye wrote:
> We should make sure off + size < sizeof(struct rte_mbuf) to avoid
> possible out-of-bounds access of free_space array, there is no issue
> currently due to the low bits of free_flags (which is adjacent to
> free_space) are always set to 0. But we shouldn't rely on it since it's
> fragile and layout of struct mbuf_dyn_shm may be changed in the future.
> This patch adds boundary check explicitly to avoid potential risk of
> out-of-bounds access.
>
> Fixes: 4958ca3a443a ("mbuf: support dynamic fields and flags")
> Cc: stable@dpdk.org
>
> Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com>
I suggest to change the title in:
mbuf: fix out-of-bounds access at dyn field register
Thomas, as Xiaolong pointed-out, it fixes a bug in the code but there is
no impact. I let you decide if it should be tagged as a fix or not, and
if it should be backported. I'll tend to say yes.
Acked-by: Olivier Matz <olivier.matz@6wind.com>
> ---
>
> V2: put the check before accessing free_space
>
> lib/librte_mbuf/rte_mbuf_dyn.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/librte_mbuf/rte_mbuf_dyn.c b/lib/librte_mbuf/rte_mbuf_dyn.c
> index d6931f847..9d6388cff 100644
> --- a/lib/librte_mbuf/rte_mbuf_dyn.c
> +++ b/lib/librte_mbuf/rte_mbuf_dyn.c
> @@ -71,7 +71,8 @@ process_score(void)
>
> for (off = 0; off < sizeof(struct rte_mbuf); off++) {
> /* get the size of the free zone */
> - for (size = 0; shm->free_space[off + size]; size++)
> + for (size = 0; (off + size) < sizeof(struct rte_mbuf) &&
> + shm->free_space[off + size]; size++)
> ;
> if (size == 0)
> continue;
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-06-11 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 15:08 [dpdk-stable] [PATCH] " Xiaolong Ye
2020-06-11 0:48 ` [dpdk-stable] [PATCH v2] " Xiaolong Ye
2020-06-11 15:03 ` Olivier Matz [this message]
2020-06-11 15:12 ` [dpdk-stable] [PATCH v3] mbuf: fix out-of-bounds access at dyn field register Xiaolong Ye
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=20200611150336.GB12564@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=xiaolong.ye@intel.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 NNTP newsgroup(s).