Most TPM chips are unaffected. Those that are will get new firmware. Virtual TPMs are affected because those are implemented using a TPM simulator based on the TCG code that has this bug. In all cases any compromise should be of the local host, not of other things unless those things are accessed using keys stored on the affected TPM. In any affected cases where the TPM can be replaced then the simplest recovery method starts with replacing the TPM and rebuilding the host then re-running any enrollment protocols that need to be re-run, otherwise flashing a compromised TPM while running on a system that can have been rootkitted is a problem.