From: Bruce Richardson <bruce.richardson@intel.com>
To: Daniil Iskhakov <dish@amicon.ru>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Wei Zhao <wei.zhao1@intel.com>, Wenzhuo Lu <wenzhuo.lu@intel.com>,
<dev@dpdk.org>, <stable@dpdk.org>,
Daniil Agalakov <ade@amicon.ru>, <sdl.dpdk@linuxtesting.org>,
<rrv@amicon.ru>
Subject: Re: [PATCH v2] net/ixgbe: fix MAC/VLAN item validation for ntuple
Date: Tue, 19 May 2026 18:00:05 +0100 [thread overview]
Message-ID: <agyXFTaQWbcJZ8jc@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260507132117.1449179-1-dish@amicon.ru>
On Thu, May 07, 2026 at 04:21:17PM +0300, Daniil Iskhakov wrote:
> When parsing an ntuple filter, the code attempts to ensure that if the
> first item is ETH or VLAN, its spec and mask are either absent or
> contain only zero fields. The current check is:
>
> if ((item->spec || item->mask) &&
> (memcmp(spec, &null_struct, size) ||
> memcmp(mask, &null_struct, size)))
>
> This condition is logically incorrect. If item->spec points to a
> zero-filled structure and item->mask is NULL, memcmp(mask) would
> dereference a NULL pointer.
>
> The intended behavior is to reject any non-zero spec or mask.
>
> Guard each memcmp() call with a check of the corresponding pointer while
> keeping a single error path.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Fixes: 46ea969177f3 ("net/ixgbe: add ntuple support to flow parser")
> Cc: stable@dpdk.org
>
> Signed-off-by: Daniil Agalakov <ade@amicon.ru>
> Signed-off-by: Daniil Iskhakov <dish@amicon.ru>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied to dpdk-next-net-intel.
Thanks,
/Bruce
prev parent reply other threads:[~2026-05-19 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 13:21 [PATCH v2] net/ixgbe: fix MAC/VLAN item validation for ntuple Daniil Iskhakov
2026-05-19 17:00 ` Bruce Richardson [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=agyXFTaQWbcJZ8jc@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=ade@amicon.ru \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=dish@amicon.ru \
--cc=rrv@amicon.ru \
--cc=sdl.dpdk@linuxtesting.org \
--cc=stable@dpdk.org \
--cc=vladimir.medvedkin@intel.com \
--cc=wei.zhao1@intel.com \
--cc=wenzhuo.lu@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