From: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
To: ohilyard@iol.unh.edu
Cc: dev@dpdk.org, stephen@networkplumber.org, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH v3] lib/rte_rib6: fix stack buffer overflow
Date: Thu, 24 Jun 2021 12:01:16 +0300 [thread overview]
Message-ID: <d9be47ec-7f06-8c8c-1edc-893210cfdafb@intel.com> (raw)
In-Reply-To: <20210621132834.21673-1-ohilyard@iol.unh.edu>
Acked-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
On 21/06/2021 16:28, ohilyard@iol.unh.edu wrote:
> From: Owen Hilyard <ohilyard@iol.unh.edu>
>
> ASAN found a stack buffer overflow in lib/rib/rte_rib6.c:get_dir.
> The fix for the stack buffer overflow was to make sure depth
> was always < 128, since when depth = 128 it caused the index
> into the ip address to be 16, which read off the end of the array.
>
> While trying to solve the buffer overflow, I noticed that a few
> changes could be made to remove the for loop entirely.
>
> Fixes: f7e861e21c ("rib: support IPv6")
>
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
> ---
> lib/rib/rte_rib6.c | 29 +++++++++++++++++++++--------
> 1 file changed, 21 insertions(+), 8 deletions(-)
>
> diff --git a/lib/rib/rte_rib6.c b/lib/rib/rte_rib6.c
> index f6c55ee45..96424e9c9 100644
> --- a/lib/rib/rte_rib6.c
> +++ b/lib/rib/rte_rib6.c
> @@ -79,20 +79,33 @@ is_covered(const uint8_t ip1[RTE_RIB6_IPV6_ADDR_SIZE],
> static inline int
> get_dir(const uint8_t ip[RTE_RIB6_IPV6_ADDR_SIZE], uint8_t depth)
> {
> - int i = 0;
> - uint8_t p_depth, msk;
> -
> - for (p_depth = depth; p_depth >= 8; p_depth -= 8)
> - i++;
> -
> - msk = 1 << (7 - p_depth);
> - return (ip[i] & msk) != 0;
> + uint8_t index, msk;
> +
> + /*
> + * depth & 127 clamps depth to values that will not
> + * read off the end of ip.
> + * depth is the number of bits deep into ip to traverse, and
> + * is incremented in blocks of 8 (1 byte). This means the last
> + * 3 bits are irrelevant to what the index of ip should be.
> + */
> + index = (depth & (UINT8_MAX - 1)) / CHAR_BIT;
> +
> + /*
> + * msk is the bitmask used to extract the bit used to decide the
> + * direction of the next step of the binary search.
> + */
> + msk = 1 << (7 - (depth & 7));
> +
> + return (ip[index] & msk) != 0;
> }
>
> static inline struct rte_rib6_node *
> get_nxt_node(struct rte_rib6_node *node,
> const uint8_t ip[RTE_RIB6_IPV6_ADDR_SIZE])
> {
> + if (node->depth == RIB6_MAXDEPTH)
> + return NULL;
> +
> return (get_dir(ip, node->depth)) ? node->right : node->left;
> }
>
>
--
Regards,
Vladimir
prev parent reply other threads:[~2021-06-24 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 16:07 [dpdk-dev] [PATCH] " ohilyard
2021-06-16 16:56 ` Stephen Hemminger
2021-06-16 17:27 ` Medvedkin, Vladimir
2021-06-16 18:18 ` [dpdk-dev] [PATCH v2] " ohilyard
2021-06-18 16:22 ` Medvedkin, Vladimir
2021-06-18 16:27 ` Medvedkin, Vladimir
2021-06-21 13:28 ` [dpdk-dev] [PATCH v3] " ohilyard
2021-06-22 7:10 ` David Marchand
2021-06-22 10:51 ` Medvedkin, Vladimir
2021-06-23 15:17 ` [dpdk-dev] [PATCH v4] rib: fix max depth IPv6 lookup ohilyard
2021-06-24 13:23 ` David Marchand
2021-06-24 9:01 ` Medvedkin, Vladimir [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=d9be47ec-7f06-8c8c-1edc-893210cfdafb@intel.com \
--to=vladimir.medvedkin@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ohilyard@iol.unh.edu \
--cc=stephen@networkplumber.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).