← WebKit — 2026-W41
7c3fb01227f09c49ccbbc661e12cd2c106a69e0d [JSC] WebAssembly debugger: a continue after `Hc<thread>` resumes the wrong VM
not a security fix
confidence 0.12
signal score 9.56
Source/JavaScriptCore/runtime
Classified as not security-relevant.
Triage note: Reworks VMManager/WasmExecutionHandler run-one-vs-run-all debugger resume logic (m_continueDebuggeeOnly, switchTarget now returns bool and rejects unknown VMs, relaxed RELEASE_ASSERTs). The null-VM guard is only reachable over the WebAssembly debug server protocol (WEBASSEMBLY_DEBUGGER), a developer tool, not attacker-reachable web content.
This commit was flagged by the signal scorer and reviewed by AI (not a human). It is listed only so the triage is auditable; there is no root-cause analysis because this is not a vulnerability fix.
Triage note: Reworks VMManager/WasmExecutionHandler run-one-vs-run-all debugger resume logic (m_continueDebuggeeOnly, switchTarget now returns bool and rejects unknown VMs, relaxed RELEASE_ASSERTs). The null-VM guard is only reachable over the WebAssembly debug server protocol (WEBASSEMBLY_DEBUGGER), a developer tool, not attacker-reachable web content.
This commit was flagged by the signal scorer and reviewed by AI (not a human). It is listed only so the triage is auditable; there is no root-cause analysis because this is not a vulnerability fix.
Structural signals: security_assert (+6.47), null_guard (+2.59), area:Source/JavaScriptCore/runtime (+2.5), large_churn (-2.0)
Before / after
Loading diff…
On This Page