If the resolver receives many queries that require recursion, there will be a corresponding increase in the number of clients that are waiting for recursion to complete. If there are sufficient clients already waiting when a new client query is received so that it is necessary to SERVFAIL the longest waiting client (see BIND 9 ARM recursive-clients limit and soft quota), then it is possible for a race to occur between providing a stale answer to this older client and sending an early timeout SERVFAIL, which may cause an assertion failure.
Created bind tracking bugs for this issue: Affects: fedora-all [bug 2164508]
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2023:2261 https://access.redhat.com/errata/RHSA-2023:2261
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2023:2792 https://access.redhat.com/errata/RHSA-2023:2792
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2022-3924