The Register: "In summary, there was a bug in atop that allowed unrelated programs to cause the atop command to fail, and to crash in more than one way. This sort of behavior should not occur and typically signals a deeper problem. This kind of unexpected behavior is the stuff of which security exploits are made. That doesn't necessarily mean this was an actual viable exploitable flaw - there's no evidence of one, so far - but it was a weird little bug, and that's a bad thing."