ISC recently discovered an issue in BIND that allows TCP connection slots to be consumed for an indefinite time frame via a specifically crafted TCP stream sent from a client. This issue is present in BIND 9.16.11 to 9.16.26 (including S editions), and 9.18.0. This issue can only be triggered on BIND servers which have keep-response-order enabled, which is not the default configuration. The keep-response-order option is an ACL block, and as such, any hosts specified within it will be able to trigger this issue on affected.
bind package in RHEL9 and bind9.16 package in RHEL8 is affected. Of course also Fedora 34-37 is affected too
Created bind tracking bugs for this issue: Affects: fedora-all [bug 2068478]
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2022:7643 https://access.redhat.com/errata/RHSA-2022:7643
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2022:8068 https://access.redhat.com/errata/RHSA-2022:8068
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-0396