It is specified in 38.214 Subclause 18.104.22.168 that
If a PDSCH scheduled by a PDCCH would overlap with resources in the CORESET containing the PDCCH, the resources corresponding to a union of the detected PDCCH that scheduled the PDSCH and associated PDCCH DM-RS are not available for the PDSCH.
Does it mean that PDSCH is rate-matched around PDCCH (like with LTE CRS in DSS), or punctured? Could you please cite also the spec that justifies your answer?
I personnally lean towards the ratematching interpretation as in 38.212 22.214.171.124, the ratematching output lengtth E_r depends on “G is the total number of coded bits available for transmission of the transport block”.