Note: The sponsor team decided to mitigate this QA finding that was outside of the winning QA report. This downgraded issue from the same warden has been included in this report for completeness. 
A slashing round can only be increased in permissionless lockAndBurn(). This subjects protocol controlled release() flow to racing conditions against lockAndBurn().
When a user is slashed they have a minimal 90-day appeal period (including following round). Suppose Alice is slashed in round 1 and suppose she appealed in round 2. If her appeal succeeds. release() can be called by RELEASER_ROLE anywhere in round 2.
The issue arises when the appeal approval is late in round 2 and release() is submitted close to the end of round 2 (lastBurnTimestamp + 90 days). release() tx has to be submitted with round 1 as input slashRound (slashRound == currentSlashRound - 1). 
https://github.com/code-423n4/2024-03-gitcoin/blob/6529b351cd72a858541f60c52f0e5ad0fb6f1b16/id-staking-v2/contracts/IdentityStaking.sol#L541-L542
Now, suppose Bob submitted lockAndBurn() tx, which settles before release() tx at the end of round 2(lastBurnTimestamp + 90 days). lockAndBurn() will burn all the slashed amount in round 1 (currentSlashRound - 1), which effectively burns Alices slashed amount. Then, it increments the round to 3. 
https://github.com/code-423n4/2024-03-gitcoin/blob/6529b351cd72a858541f60c52f0e5ad0fb6f1b16/id-staking-v2/contracts/IdentityStaking.sol#L513-L515
Then, when release() settles, if (slashRound < currentSlashRound - 1) will be true, causing tx to revert. Alice lost the refund. 
Alex the Entreprenerd (judge) commented:
Note: For full discussion, see here.
Gitcoin mitigated:
Status: Mitigation confirmed. Full details in reports from oakcobalt, Stormy and 0xDING99YA.
