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.
As reported by covscan:
4. nftables-0.6/src/evaluate.c:2016: var_compare_op: Comparing "base" to null implies that "base" might be null.
8. nftables-0.6/src/evaluate.c:2021: var_deref_model: Passing null pointer "base" to "proto_find_num", which dereferences it.
10. nftables-0.6/src/proto.c:79:3: deref_parm: Directly dereferencing parameter "base".
# 77|
# 78| for (i = 0; i < array_size(base->protocols); i++) {
# 79|-> if (base->protocols[i].desc == desc)
# 80| return base->protocols[i].num;
# 81| }
I am not sure if this is valid, it seems like 'base' being NULL is a very special case. Though I couldn't yet verify it's sane either, so better keep this on my todo.
Fixed upstream, need to backport this commit:
commit 7241af302bbe56908fa87b17799048bfe884e35f
Author: Phil Sutter <phil>
Date: Tue Aug 30 19:39:51 2016 +0200
evaluate: reject: Have a generic fix for missing network context
Commit 17b495957b29e ("evaluate: reject: fix crash if we have transport
protocol conflict from inet") took care of a crash when using inet or
bridge families, but since then netdev family has been added which also
does not implicitly define the network context. Therefore the crash can
be reproduced again using the following example:
nft add rule netdev filter e1000-ingress \
meta l4proto udp reject with tcp reset
In order to fix this in a more generic way, have stmt_evaluate_reset()
fall back to the generic proto_inet_service irrespective of the actual
proto context.
Signed-off-by: Phil Sutter <phil>
Signed-off-by: Pablo Neira Ayuso <pablo>
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-2017:2047
As reported by covscan: 4. nftables-0.6/src/evaluate.c:2016: var_compare_op: Comparing "base" to null implies that "base" might be null. 8. nftables-0.6/src/evaluate.c:2021: var_deref_model: Passing null pointer "base" to "proto_find_num", which dereferences it. 10. nftables-0.6/src/proto.c:79:3: deref_parm: Directly dereferencing parameter "base". # 77| # 78| for (i = 0; i < array_size(base->protocols); i++) { # 79|-> if (base->protocols[i].desc == desc) # 80| return base->protocols[i].num; # 81| } I am not sure if this is valid, it seems like 'base' being NULL is a very special case. Though I couldn't yet verify it's sane either, so better keep this on my todo.