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.

The following command crashes nft utility reproducibly:

# nft add rule ip6 test ftest ip6 nexthdr ipv6-frag counter

Analysis of the cause using gdb and looking at differences between version 0.6 and upstream (which works fine) shows we're missing the following commit:

commit 3503738f77cdbe521da1054a37f59ac2e442b4cf
Author: Florian Westphal <fw>
Date:   Mon Jun 6 21:52:28 2016 +0200

    payload: don't update protocol context if we can't find a description
    
    Since commit
    20b1131c07acd2fc ("payload: fix stacked headers protocol context tracking")
    we deref null pointer if we can't find a description for the desired
    protocol, so "ip protocol 254" crashes while testing protocols 6 or 17
    (tcp, udp) works.
    
    Also add a test case for this.
    
    Closes: https://bugzilla.netfilter.org/show_bug.cgi?id=1072
    Signed-off-by: Florian Westphal <fw>
    Acked-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