Yes, that's it:
1. Restore from last known 'good' backup.
2. Restore every transaction log backup taken since then, including taking log backups from the corrupted database before shutting it down.

Please continue taking transaction log backups on the damaged database while you prepare your restore. It has suffered significant loss, but you can recover everything, including capturing all changes made to the database, if you keep taking log backups.

Disk corruption on  data files (at least the kind shown in your CHECKDB output) is not written to the transaction log, unless the log file got damaged in the incident. Because the transaction log does not contain the instructions on how to cause the damage to the data files, restoring from a full backup taken before the incident and using log backups from before and after the incident won't include the damage.
If there was damage, but it occurred to an area of the log that had already been backed up, there will be no data loss.

If the event also wiped your backups, then you're pretty much out of options.