[EC]DHE_RSA means that the shared secret between the client and server is computed via Diffie-Hellman. In the case of DHE each session has it's own DH parameters (DHE = elliptic curve Diffie-Hellman ephemeral) which is done to provide forward secrecy. It goes something like this (over simplified):
- Server generates some DH parameters.
- Server signs the DH params with it's long term key (i.e. your RSA 2048 key) and sends the params and signature to the client.
- Client verifies the signature for the params against the public RSA 2048 key contained in the servers certificate.
- If the signature is good the client and server use DH with these params to established a shared secret from which they derive keys for the session.
So if your server generates DH params that are too small (e.g. 512 bits) or it supports DHE_EXPORT (or anything else mentioned in the logjam paper) then you are still vulnerable to the attack. You can reference this answer for good discussion on the security of DH params. The key insight is that the long-term RSA key is being used to ensure that the parameters sent to the client were not tampered with and generated by the server. The actual key generation / derivation is done via DH.
(It should be noted that ECDHE does not have this pitfall, so any cipher suite with ECDHE_RSA should be fine).