1. If code is "correct" but non-performant when it needs to be performant, then it's not correct.
2. If code is "correct" but unmaintainable when it needs to be maintainable, then it's not correct.
3. If code is "correct" but does not fit standards when it needs to fit standards, then it's not correct.
4. If code is "correct" but not secure when it needs to be secure, then it's not correct.
5. If code is "correct" but not correct when it needs to be correct, then it's not correct.
6. If code is "correct" but legally risky when it needs to be legally not risky, then it's not correct.
7. If code is "correct" but people think it's incorrect when they need to think it's correct, then it's not correct.
The person who submits the code for code review is effectively asserting that the code meets the quality standards of the project to which they are submitting the code. If it doesn't meet those standards, then it's not correct.