Which SQL isolation level prevents dirty reads but still allows non-repeatable reads?

Explanation

READ COMMITTED lets a transaction see only committed data (no dirty reads), but a row read twice may change between reads; REPEATABLE READ and SERIALIZABLE forbid that.