All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 2036] net/octeontx: nr_port write runs past a one byte stack struct
Date: Sun, 13 Sep 2026 17:35:18 +0000	[thread overview]
Message-ID: <bug-2036-3@https.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=2036

            Bug ID: 2036
           Summary: net/octeontx: nr_port write runs past a one byte stack
                    struct
           Product: DPDK
           Version: 26.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

drivers/net/octeontx/octeontx_ethdev.c

parse_integer_arg() stores an int:

        static int
        parse_integer_arg(const char *key __rte_unused,
                        const char *value, void *extra_args)
        {
                int *i = (int *)extra_args;

                *i = atoi(value);

The caller passes &params->nr_port, which is a uint8_t and the only member
of a struct octeontx_vdev_init_params living on the stack:

        struct octeontx_vdev_init_params {
                uint8_t nr_port;
        };

So "nr_port=1" writes four bytes into a one byte struct, three of them past
its end. Worst of the set because the overrun leaves the object entirely.

Fixes: f7be70e5130e ("net/octeontx: add net device probe and remove")

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2026-09-13 17:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-2036-3@https.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.