CVE-2023-6516
HIGHDescription
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.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Moderate risk: more likely to be exploited than 64% of all known CVEs.
References
Related Vulnerabilities
Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-50387 | High | 7.5 | 100% | - | Fix |
| CVE-2019-11478 | Medium | 5.3 | 95% | - | Fix |
| CVE-2019-11479 | High | 7.5 | 92% | - | Fix |
| CVE-2024-27316 | High | 7.5 | 91% | - | Fix |
| CVE-2022-30522 | High | 7.5 | 90% | - | Fix |
| CVE-2019-9515 | High | 7.5 | 87% | - | Fix |
Common questions
How do I fix CVE-2023-6516?
Published advisories record a fix for 96 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2023-6516 being actively exploited?
Not that we know of. CVE-2023-6516 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 1.1% is the estimated probability that it will be exploited in the next 30 days. That is higher than 64% of all scored CVEs.
How severe is CVE-2023-6516?
CVE-2023-6516 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2023-6516 affect?
Published advisories record a fix for bind (Amazon), bind-chroot (Amazon), bind-debuginfo (Amazon), bind-debugsource (Amazon), and 92 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2023-6516
Markdown
[](https://tridentstack.com/cve/CVE-2023-6516)HTML
<a href="https://tridentstack.com/cve/CVE-2023-6516"><img src="https://tridentstack.com/cve/badge/CVE-2023-6516.svg" alt="CVE-2023-6516"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-17.