CoreCVE
Back

HIGH

Specific recursive query patterns may lead to an out-of-memory condition

Published Feb 13, 2024

Description

To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first allocated and then queued for later processing. It was discovered that if the resolver is continuously processing query patterns triggering this type of cache-database maintenance, `named` may not be able to handle the cleanup events in a timely manner. This in turn enables the list of queued cleanup events to grow infinitely large over time, allowing the configured `max-cache-size` limit to be significantly exceeded. This issue affects BIND 9 versions 9.16.0 through 9.16.45 and 9.16.8-S1 through 9.16.45-S1.

Affected products

Remediation

Vendor solution

Upgrade to the patched release most closely related to your current version of BIND 9: 9.16.48 or 9.16.48-S1.

Red Hat mitigation

There is no available mitigation for this issue other than applying the required fixes via the released updates.

Metrics

Weaknesses (3)

CWE-400

Uncontrolled Resource Consumption

CWE-770

Allocation of Resources Without Limits

CWE-789

References (9)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner isc
Published Feb 13, 2024
Updated Feb 13, 2025
Reserved Dec 5, 2023
Link CVE-2023-6516
CISA Vulnrichment
Updated Feb 20, 2024
NVD
Status Modified
Modified Jun 17, 2026
Link CVE-2023-6516
Red Hat
Severity Important
Public date Feb 13, 2024
Links CVE-2023-6516 - Bugzilla