when liquidateBorrower function is called it gets the debt of the user, and then gets the normalization, and then applies an additional normalization step using rayMul. However the issue here is that the LendingPool::getUserDebt function is already returning the scaled debt amount by applying rayMul with the usageIndex, this causes a situation where the userdebt is overscaled.
Overestimation of Debt: Since getUserDebt already applies rayMul to scale the debt, performing another rayMul in liquidateBorrower results in an overly inflated debt value.
manual review
Remove the extra scaling in liquidateBorrower
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.