{"version":"2.1.265","anchor":"interrupt-handling-variable-fix-in-queued-interrupt-path","canonical_anchor":"interrupt-handling-variable-fix-in-queued-interrupt-path","heading":"Interrupt handling: variable fix in queued-interrupt path","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/interrupt-handling-variable-fix-in-queued-interrupt-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Interrupt handling: variable fix in queued-interrupt path\n\nA queued-interrupt code path now stores the correct variable instead of a mismatched one\n\n**Unclear.** The finding doesn't state what the old, incorrect variable caused to go wrong in practice.\n\n**What**\n\nIn the part of interrupt handling that runs when there's no live session, the value saved into `pendingInterrupt` was changed from one local variable to a different one.\n\n**Why**\n\nThis looks like a correctness fix ensuring the right interrupt value is queued and later acted on when no live session is present.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}