DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Manish Kurup <manish.kurup@broadcom.com>
To: dev@dpdk.org
Cc: kishore.padmanabha@broadcom.com
Subject: [PATCH 0/2] net/bnxt: fix two ULP parser/mapper safety issues
Date: Mon,  5 Oct 2026 10:17:25 -0500	[thread overview]
Message-ID: <20261005151727.1706155-1-manish.kurup@broadcom.com> (raw)

Two unrelated hardening fixes in the ULP parser/mapper found during
review:

- Patch 1 caps a header-field memcpy() at the field's spec size,
  fixing a potential overflow when the source value is larger than
  the destination field.

- Patch 2 replaces a variable-length array sized by caller input
  with a heap allocation, avoiding unbounded stack growth.

Dakota Sicher (2):
  net/bnxt: cap memcpy at field size
  net/bnxt: replace VLA with heap allocation

 drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c | 10 ++++++++--
 drivers/net/bnxt/tf_ulp/ulp_rte_parser.c | 10 ++++++++++
 2 files changed, 18 insertions(+), 2 deletions(-)

-- 
2.31.1


             reply	other threads:[~2026-10-05 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 15:17 Manish Kurup [this message]
2026-10-05 15:17 ` [PATCH 1/2] net/bnxt: cap memcpy at field size Manish Kurup
2026-10-05 15:17 ` [PATCH 2/2] net/bnxt: replace VLA with heap allocation Manish Kurup

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=20261005151727.1706155-1-manish.kurup@broadcom.com \
    --to=manish.kurup@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=kishore.padmanabha@broadcom.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