A security issue has been found in procps-ng <= 3.3.14, in the xcalloc() and xrealloc() functions, where the use of an unsigned int instead of a size_t could lead to integer overflow on 64-bit platforms.
A security issue has been found in procps-ng <= 3.3.14, in the xcalloc() and xrealloc() functions, where the use of an unsigned int instead of a size_t could lead to integer overflow on 64-bit platforms.
https://www.qualys.com/2018/05/17/procps-ng-audit-report-advisory.txt
Related patch in Qualys' tarball: 0035-proc-alloc.-Use-size_t-not-unsigned-int.patch
Vulmon