DPDK usage discussions
 help / color / mirror / Atom feed
From: NAGENDRA BALAGANI <nagendra.balagani@oracle.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: Kapil Kumar Jain <kapil.k.jain@oracle.com>
Subject: Clarification on Possible Buffer Overflow Issues Reported by Fortify Tool
Date: Fri, 10 Oct 2025 11:16:54 +0000	[thread overview]
Message-ID: <DM6PR10MB41241F954D9C9680F98B29E996EFA@DM6PR10MB4124.namprd10.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2115 bytes --]

Hi Team,

While running Fortify static code analysis on our codebase, which uses DPDK, we noticed some potential buffer overflow issues being flagged in DPDK library calls. These seem like false positives at first glance, but we want to double-check with the community and maintainers to make sure there are no hidden issues.

Could you please review these findings or let us know if there are any known false positives related to this. I raised a Bug  https://bugs.dpdk.org/show_bug.cgi?id=1748 for the same.

here are the detailed Fortify reports with exact file paths and line numbers for your reference.
### Instance 1:  rte_crypto.h Line 207
memset(op->asym, 0, sizeof(struct rte_crypto_asym_op));

Tool Description : The function __rte_crypto_op_reset() in rte_crypto.h writes outside the bounds of asym on line 207, which could corrupt data, cause the program to crash, or lead to the execution of malicious code.

Analysis Trace
rte_crypto.h:181 - Buffer asym Declared
rte_crypto.h:207 - memset()
Buffer Size: 0 bytes Write Length: 168 bytes

### Instance 2: rte_crypto_sym.h: 885
memset(op, 0, sizeof(*op));
Tool Description: The program writes outside the bounds of allocated memory, which could corrupt data, crash the program, or lead to the execution of malicious code.
Analysis Trace
rte_crypto.h:204 - Caller: __rte_crypto_op_reset
Buffer Size: 0
rte_crypto_sym.h:885 - memset()
Buffer Size: 0 bytes Write Length: 64 bytes [var 0] op.$offset: 0

### Instance3: rte_lpm.h: 347
            tbl24_indexes[i] = ips[i] >> 8;
Tool Description: The function rte_lpm_lookup_bulk_func() in rte_lpm.h writes outside the bounds of tbl24_indexes on line 347, which could corrupt data, cause the program to crash, or lead to the execution of malicious code.
Analysis Trace
rte_lpm.h:339 - Buffer tbl24_indexes Allocated
rte_lpm.h:347 - Assignment to tbl24_indexes
Buffer Size: 262143 bytes Write Length: 1048572 bytes [var 0] tbl24_indexes.$offset: 0 [var 1] i: 262142
Thank you in advance for your support and guidance.
Regards,
Nagendra



Confidential - Oracle Internal

[-- Attachment #2: Type: text/html, Size: 5438 bytes --]

                 reply	other threads:[~2025-10-10 11:17 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=DM6PR10MB41241F954D9C9680F98B29E996EFA@DM6PR10MB4124.namprd10.prod.outlook.com \
    --to=nagendra.balagani@oracle.com \
    --cc=kapil.k.jain@oracle.com \
    --cc=users@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;
as well as URLs for NNTP newsgroup(s).