On this page (7 sections)

Ubuntu has published security notice USN-9128-1 for YADIFA, a DNS server. According to Ubuntu's notice, YADIFA did not check for infinite pointer loops when parsing DNS packets, so a remote attacker could possibly make it consume excessive CPU and cause a denial of service.

If you run YADIFA on an Ubuntu host to serve DNS for your domains, this notice is for you. The source we have is short, so this article separates what the notice confirms from general background and guidance, and labels the latter as such.

What was disclosed

The notice describes a single issue: YADIFA did not check for infinite pointer loops while parsing DNS packets. The only stated consequence is that a remote attacker could possibly drive CPU usage up and deny service. The notice text we reviewed does not mention data theft, code execution or changes to DNS records.

That text also does not list a CVE identifier, a CVSS score, the affected Ubuntu releases, the fixed package versions or whether the issue is being exploited. We have not guessed at any of these. Check the notice page directly for the release and version table before you patch.

Only one publisher covers this story so far, and it is the Ubuntu notice itself. Treat any detail beyond its short description as unconfirmed.

The weakness in plain terms

General background, not from the notice: DNS messages can shorten repeated domain names by using pointers that refer back to an earlier part of the same message. Software that follows these pointers must make sure the chain of references always ends. A parser with no such check can, in principle, keep following references without finishing, which ties up the CPU. That is the weakness class the notice names.

The notice itself says only what is quoted above. It does not say how many packets it takes to cause real disruption, or whether an attacker needs any special access. In general, a DNS server that is reachable from the internet is exposed to traffic from unknown senders, so reachability is the first thing to check.

Who is realistically exposed

  • Anyone running YADIFA as a DNS server, especially one reachable from the internet.
  • Hosting providers and agencies that run their own nameservers for customer domains.
  • Teams with a YADIFA instance on an internal network, where the risk depends on who can send packets to it.

If you use a managed DNS provider and do not run YADIFA yourself, this notice does not require action on your side. As general background, if your own nameserver stalls, services that depend on resolving your domain, such as your website and email, can be affected for visitors who cannot get a cached answer.

How to check whether you are affected

First find out whether YADIFA is installed at all. The command below lists installed packages whose names contain yadifa on Debian and Ubuntu systems. Note the exact package name in the output; you will need it later. No output means it is not installed through the package manager.

List installed YADIFA packages (Debian/Ubuntu)Shell
dpkg -l | grep -i yadifa

Then check whether a YADIFA process is running. This read-only command shows processes with yadifa in the name. It shows only running processes, not which ports they listen on.

Check for a running YADIFA process (Linux)Shell
ps aux | grep -i [y]adifa

To see whether something is listening for DNS traffic, list listening UDP and TCP sockets and look for port 53 or the YADIFA process. This is read-only.

List listening sockets with process names (Linux, run as root)Shell
sudo ss -lntup | grep -E ':53\b|yadifa'

If the socket is bound to a public address, the service is reachable from the internet and patching is more urgent. If it is bound only to a loopback or internal address, exposure depends on who can reach that network.

What to do now

  1. Open USN-9128-1 and find your Ubuntu release and the fixed package version.
  2. Apply the updates the notice lists using your normal patch process.
  3. Restart the YADIFA service after the upgrade so the fixed code is running.
  4. Confirm the installed version matches the one in the notice.
  5. Limit who can reach the DNS service where your design allows it, for example with firewall rules for trusted networks. This is general hardening advice, not something the notice states.
  6. Set up CPU alerts on your nameservers so a sustained spike is noticed quickly.

First, refresh the package lists and see which updates are pending. The first command only refreshes the package index and the second only lists upgradable packages; look for the YADIFA package name you found earlier.

Refresh package lists and list pending upgrades (Debian/Ubuntu)Shell
sudo apt update
apt list --upgradable

If the YADIFA package appears as upgradable and the version matches the fixed one in the Ubuntu notice, upgrade just that package. Replace the placeholder with the exact package name from the earlier dpkg output; do not run it with the placeholder unchanged.

Upgrade only the YADIFA package (Debian/Ubuntu, replace the placeholder)Shell
sudo apt install --only-upgrade <package-name>
Caution. Restarting a DNS server briefly interrupts name resolution. If you have more than one nameserver, patch and restart them one at a time.

Package upgrades often restart the service for you, but do not assume it. The service name is not given in the notice, so first list the matching systemd units to find it. This is read-only.

Find the YADIFA service name (systemd-based Ubuntu)Shell
systemctl list-units --all | grep -i yadifa

Then restart that service and check its status, replacing the placeholder with the unit name from the previous output.

Restart the YADIFA service and check status (replace the placeholder)Shell
sudo systemctl restart <service-name>
systemctl status <service-name>

Finally, run dpkg -l | grep -i yadifa again and compare the installed version with the one in the notice. Then test that your domains still resolve from a machine outside your network.

Detection and monitoring afterwards

The notice does not describe log signatures or indicators of attack. As general guidance only, a denial of service of this kind would typically appear as sustained high CPU on the DNS process, so that is the most practical thing to watch.

To see whether the DNS process is currently consuming a lot of CPU, take a one-time snapshot of the busiest processes. This is read-only.

Show the top CPU-consuming processes once (Linux)Shell
ps aux --sort=-%cpu | head -n 5
  • Alert on sustained CPU use by the DNS process, not just brief spikes.
  • Run external checks that resolve your own domains from outside your network, so you notice when answers stop.
  • Keep at least two nameservers on separate hosts so one stalled server does not take your domain offline.
  • Record the date you patched each nameserver, so you can show which hosts were still on the old version if questions come up later.

For outside checks, Webforta Monitor covers uptime, certificate, DNS and header-change monitoring, which helps you notice when your site stops resolving. Our guide to uptime monitoring explains how to set up useful alerts, and DDoS protection basics covers wider resilience planning.

Timeline

What the source confirms
DateEvent
2026-11-17Ubuntu publishes USN-9128-1 describing the YADIFA pointer loop issue
Not statedDate of discovery, reporter, CVE assignment, fixed versions and exploitation status are not given in the source we reviewed

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. USN-9128-1: YADIFA vulnerabilityubuntu.com ·
  • Ubuntu
  • YADIFA
  • DNS
  • denial of service
  • USN