You can't fix that.
If you do recover the DB and run checkDB, you can't get it back into restoring state, and without running checkDB, it won't come out of suspect.
Drop it, restore a fresh backup from the primary, and then check the IO subsystem and see if you can find what caused the corruption.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass