Bug 2556415 (CVE-2026-97313) - CVE-2026-97313 bind: bind: Denial of service via assertion failure in RPZ query processing
Summary: CVE-2026-97313 bind: bind: Denial of service via assertion failure in RPZ que...
Keywords:
Status: NEW
Alias: CVE-2026-97313
Deadline: 2026-10-21
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2558427 2558426
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-20 19:59 UTC by OSIDB Bzimport
Modified: 2026-11-04 08:10 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:92419 0 None None None 2026-10-29 17:48:06 UTC
Red Hat Product Errata RHSA-2026:93072 0 None None None 2026-10-30 17:36:27 UTC
Red Hat Product Errata RHSA-2026:93610 0 None None None 2026-11-02 12:07:24 UTC
Red Hat Product Errata RHSA-2026:94011 0 None None None 2026-11-02 18:52:20 UTC
Red Hat Product Errata RHSA-2026:94115 0 None None None 2026-11-03 01:22:22 UTC
Red Hat Product Errata RHSA-2026:94277 0 None None None 2026-11-03 03:50:24 UTC
Red Hat Product Errata RHSA-2026:94278 0 None None None 2026-11-03 03:55:25 UTC
Red Hat Product Errata RHSA-2026:95017 0 None None None 2026-11-04 07:45:14 UTC
Red Hat Product Errata RHSA-2026:95048 0 None None None 2026-11-04 08:10:00 UTC

Description OSIDB Bzimport 2026-10-20 19:59:37 UTC 
A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may exit with an assertion failure, resulting in a denial of service. To be vulnerable, the BIND server must allow recursive queries and have at least two RPZ zones configured: one with the default setting of "recursive-only yes", and the other with "recursive-only no".
Comment 2 Jon Orris 2026-10-29 17:48:04 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:92419 https://access.redhat.com/errata/RHSA-2026:92419
Comment 3 Jon Orris 2026-10-30 17:36:25 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:93072 https://access.redhat.com/errata/RHSA-2026:93072
Comment 4 Jon Orris 2026-11-02 12:07:23 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:93610 https://access.redhat.com/errata/RHSA-2026:93610
Comment 5 Jon Orris 2026-11-02 18:52:19 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:94011 https://access.redhat.com/errata/RHSA-2026:94011
Comment 6 Jon Orris 2026-11-03 01:22:20 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10.0 Extended Update Support

Via RHSA-2026:94115 https://access.redhat.com/errata/RHSA-2026:94115
Comment 7 Jon Orris 2026-11-03 03:50:22 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On

Via RHSA-2026:94277 https://access.redhat.com/errata/RHSA-2026:94277
Comment 8 Jon Orris 2026-11-03 03:55:24 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:94278 https://access.redhat.com/errata/RHSA-2026:94278
Comment 9 Jon Orris 2026-11-04 07:45:13 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.8 Telecommunications Update Service

Via RHSA-2026:95017 https://access.redhat.com/errata/RHSA-2026:95017
Comment 10 Jon Orris 2026-11-04 08:09:58 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:95048 https://access.redhat.com/errata/RHSA-2026:95048
Note You need to log in before you can comment on or make changes to this bug.