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.
+++ This bug was initially created as a clone of Bug #1921152 +++
Description of problem:
In fix of CVE-2020-25686 was created regression, which applies when multiple address families send request for the same name. In that case, only one family receives responses.
Version-Release number of selected component (if applicable):
dnsmasq-2.83-1.fc33
How reproducible:
100%
Steps to Reproduce:
1. send multiple ipv4 requests for one name
2. send multiple ipv6 requests for the same name
3. both address families join single request
Actual results:
Only half of responses arrives, one address family will not receive
Expected results:
Both address families receive all responses.
Additional info:
Discovered after new upstream release, reported on mailing list[1]. Fixed by release of dnsmasq-2.84
1. https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q1/014613.html
Possible workaround is reducing priority of one family, for example IPv6. If most clients query using the same family, this error would not be visible. It would show only when both IPv4 and IPv6 is used for the same name.
Another workaround would be serving each address family from different dnsmasq instance.
dnsmasq --bind-interfaces --listen-address=<local-ipv4-address> ...
dnsmasq --bind-interfaces --listen-address=<local-ipv6-address> ...
Operating multiple instances usually requires more work. Some port redirection might work as well, listening on IPv6 socket and forwarding to ipv4. It would lose source address infromation that way, only localhost would be in logs.
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 (Moderate: dnsmasq security and bug fix update), 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/RHSA-2021:4153