CVE-2026-93007

Dnsmasq: dnsmasq: tcp/53 child-slot exhaustion starves dnssec validation

  • Medium 5.3

Description

A flaw was found in dnsmasq. The TCP DNS service uses a small fixed pool of child processes and does not set a receive timeout on client connections. A remote attacker can open idle TCP connections to port 53 and occupy the entire pool, preventing new TCP DNS connections and DNSSEC validation that requires TCP fallback. UDP DNS resolution continues, and occupied slots are released after a fixed lifetime.

Key facts

Published
29 Oct 2026
Last changed
6 Nov 2026
Assigned by
redhat
EPSS
0.427% likely to be exploited in the next 30 days, higher than 37.449% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.3CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

What to do

  • The following measures reduce risk: 1. Increase the TCP connection limit with --max-tcp-connections=<N> to raise the number of connections an attacker must hold. 2. Limit per-source TCP connections to port 53 with firewall rules, for example iptables connlimit on tcp/53. 3. Restrict which hosts can reach TCP port 53 if TCP DNS is not required from untrusted networks.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Ceph Storage 9
  • Default status: affected
Red HatRed Hat Enterprise Linux 10
  • Default status: affected
Red HatRed Hat Enterprise Linux 6
  • Default status: affected
Red HatRed Hat Enterprise Linux 7
  • Default status: affected
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 9
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected
Red HatRed Hat OpenStack Platform 13 (Queens)
  • Default status: affected
Red HatRed Hat OpenStack Platform 18.0
  • Default status: affected

Timeline

  1. 14 Sep 2026 Reported to Red Hat.
  2. 28 Oct 2026 Made public.
  3. 29 Oct 2026 Published

Weakness

References