Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1349039[details]
added issues
Coverity tool found a number of potential issues in rebased libnftnl code base, see attachment for details.
All warnings about potential NULL pointer dereference in nftnl_chain_set_data() are invalid: Covscan missed that initial call to nftnl_assert_validate() will lead to calling exit() if 'data' is NULL.
Possibly negative return of time(NULL) in nftnl_batch_is_supported() was deemed unproblematic by upstream maintainer: https://www.spinics.net/lists/netfilter-devel/msg43429.html
Potential NULL pointer deref in nftnl_gen_set_data() is invalid for the same reason as in nftnl_chain_set_data().
Potential NULL pointer deref in nftnl_obj_set_data() is invalid as well, since the function calls nftnl_assert_validate(), too.
Potential NULL pointer deref in nftnl_rule_set_data() is invalid for the same reason as above.
Warning about uninitialized variable 'attr' in nftnl_rule_parse_expr() is invalid: mnl_attr_for_each_nested() initializes it.
Potential NULL pointer deref in nftnl_set_set_data() falls into the same category as those above, the function protects access to 'data' by a call to nftnl_assert_validate().
Warning about uninitialized variable 'attr' in nftnl_set_elems_parse() is invalid as well since it is passed to mnl_attr_for_each_nested().
Remaining issues addressed in a series of patches for upstream: https://marc.info/?l=netfilter-devel&m=151328044511316&w=2
Upstream accepted. The list of patches to backport is:
4177002b26f02 ("data_reg: Add a missing break in nftnl_data_reg_snprintf")
fd9ab5c922cd8 ("gen: Remove a pointless call to mnl_nlmsg_get_payload()")
8f228f6842494 ("object: Avoid returning garbage in nftnl_obj_do_parse()")
dbaf6ea8f6a1a ("ruleset: Avoid reading garbage in nftnl_ruleset_cb()")
8bcf10b504c69 ("set_elem: Don't return garbage in nftnl_set_elems_parse()")
57f85977ed72e ("trace: Check return value of mnl_attr_parse_nested()")
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1027
Created attachment 1349039 [details] added issues Coverity tool found a number of potential issues in rebased libnftnl code base, see attachment for details.