Under the hood
A queued-interrupt code path now stores the correct variable instead of a mismatched one
What
In 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.
Why
This looks like a correctness fix ensuring the right interrupt value is queued and later acted on when no live session is present.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding doesn't state what the old, incorrect variable caused to go wrong in practice.