The issue arises because ntpd relies on the underlying operating system to protect it from requests that impersonate reference clocks. Since reference clocks are treated like other peers and stored in the same structure, any packet with a source IP address of a reference clock that reaches the receive() function will be treated as a trusted peer. This poses a risk to systems that lack typical martian packet filtering, which would block these packets, allowing an attacker to potentially control the time on the system.