From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 2104] pipeline: table entry parser accepts actions not belonging to the table
Date: Thu, 12 Nov 2026 17:30:08 +0000 [thread overview]
Message-ID: <bug-2104-3@https.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=2104
Bug ID: 2104
Summary: pipeline: table entry parser accepts actions not
belonging to the table
Product: DPDK
Version: 26.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Found by build with GCC 16 and -fanalyzer flag.
rte_swx_ctl_pipeline_table_entry_read() (lib/pipeline/rte_swx_ctl.c:3131) finds
the action with action_find(ctl, tokens[1]), which searches all pipeline
actions. It does not check that the action is one of the table's actions.
entry->action_data is allocated from table->params.action_data_size (:321), or
left NULL when that is 0. table_entry_action_argument_read() (:2896) then
copies the arguments into it. An entry line naming an action with more argument
bytes than the table allows writes past the buffer, or to NULL.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-11-12 17:30 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-2104-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox