Re: Clarification on Possible Buffer Overflow Issues Reported by Fortify Tool

Re: Clarification on Possible Buffer Overflow Issues Reported by Fortify Tool

[NAGENDRA BALAGANI]

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

Hi Team,
This is a gentle follow-up on my earlier mail regarding the Fortify static analysis findings in DPDK, for which I had also raised Bug 1748.

Could you please let us know if there is any update or guidance from the community/maintainers on whether these are known false positives or if they need further investigation.

Thank you for your time and support.

Regards,
Nagendra



Confidential – Oracle Internal

From: NAGENDRA BALAGANI <nagendra.balagani@oracle.com>
Date: Friday, 10 October 2025 at 4:46 PM
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

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


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

Re: Clarification on Possible Buffer Overflow Issues Reported by Fortify Tool

[Stephen Hemminger]

On Thu, 5 Feb 2026 06:58:29 +0000
NAGENDRA BALAGANI <nagendra.balagani@oracle.com> wrote:

> Hi Team,
> This is a gentle follow-up on my earlier mail regarding the Fortify static analysis findings in DPDK, for which I had also raised Bug 1748.
> 
> Could you please let us know if there is any update or guidance from the community/maintainers on whether these are known false positives or if they need further investigation.
> 
> Thank you for your time and support.

Did you file bugzilla entries and/or submit patches?