Just to add to this, it appears to be a Symantec NetBackup thing. We experienced the same issue again today, and when I restored the NetBackup backup (corrupted database - to another server with the same version of SQL), DBCC CHECKDB returned no errors.

I then took a copy_only backup and restored it (same server as above) and CHECKDB returned the errors as expected.