Submitted by maxzuvex
https://github.com/code-423n4/2025-04-cabal/blob/5b5f92ab4f95e5f9f405bbfa252860472d164705/sources/cabal.move#L996-L998
https://github.com/code-423n4/2025-04-cabal/blob/5b5f92ab4f95e5f9f405bbfa252860472d164705/sources/cabal.move#L1051-L1053
When a user burns the entire remaining supply of a Cabal LST (sxINITorCabalLPT) viainitiate_unstake, the followup processing step always aborts with a dividebyzero and the user can never exit.
Because the burn happened in a prior committed transaction, every retry of process_*_unstake gets the same supply == 0 state and fails again, so the users INIT / LP is permanently locked and it makes a DoS for the final staker of that pool.
Impact:
If an address burns the last sxINIT/LPT in circulation, every call to process_*_unstake reverts with EDIVISION_BY_ZERO, so noUnbondingEntry is recorded and the underlying INIT / LP can never be claimed. The final stakers funds are permanently locked and causes a poollevel denial of service.
In process_xinit_unstake and process_lp_unstake:
