# CVE-2026-99059: wireguard: noise: reject response consumption after intermediate initiation CVE-2026-99059 is fixed in 19 products on 1 platform, first by DEBIAN-CVE-2026-99059, released October 24, 2026. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2026-99059 - Priority: High - CVSS: 7.7 (Important) - EPSS: 0.0051 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Oct 23, 2026 - Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-99059 ## Description In the Linux kernel, the following vulnerability has been resolved: wireguard: noise: reject response consumption after intermediate initiation Two threads begin processing the identical response message, received twice. The first thread, A, runs. While it's running, the second one, B, gets partway through, and during that slow calculation, or even while blocking on down_write(), A completes and then also a handshake initiation that's already been queued up runs in thread C, which itself takes that same down_write(). The handshake initiation creation succeeds, and sets the state back to waiting-for-response, and calls up_write(), at which point thread B resumes, because either its finished its calculations or was finally allowed to acquire down_write(). Thread B then copies the state back to the peer, and begins a new session, using that state, which is the same session as the one made in thread A. Thread A Thread B Thread C down_read() sA = handshake->state memcpy(cA, handshake->crypto) up_read() if (sA != 1) goto fail slow_crypto(cA) down_read() sB = handshake->state memcpy(cB, handshake->crypto) up_read() if (sB != 1) goto fail slow_crypto(cB) down_write() if (sA != handshake->state) goto fail memcpy(handshake->crypto, cA) handshake->state = 2 up_write() down_write() if (handshake->state != 2) goto fail derive_session(handshake->crypto) up_write() down_write() slow_crypto(handshake->crypto) handshake->state = 1 up_write() down_write() if (sB != handshake->state) goto fail memcpy(handshake->crypto, cB) handshake->state = 2 up_write() down_write() if (handshake->state != 2) goto fail derive_session(handshake->crypto) up_write() This seems basically impossible to hit in a meaningful way in practice, but ensure that it absolutely cannot happen by comparing the ephemeral private key that's on the stack with the latest one that the peer's handshake state has. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool6.12 amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | bpftool6.12-debuginfo amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel-livepatch-6.12.113-138.209 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel6.12 amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel6.12-debuginfo amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel6.12-debuginfo-common-aarch64 amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel6.12-debuginfo-common-x86_64 amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel6.12-devel amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel6.12-headers amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel6.12-modules-extra amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel6.12-modules-extra-common amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel6.12-tools amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel6.12-tools-debuginfo amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | kernel6.12-tools-devel amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | linux Debian 13.5 (trixie) | 6.12.113-1 | [DEBIAN-CVE-2026-99059](https://patchblox.com/security/data/fix/linux/debian-cve-2026-99059.md) | Oct 24, 2026 | | Linux | linux Debian 14 | 7.2.11-1 | [DEBIAN-CVE-2026-99059](https://patchblox.com/security/data/fix/linux/debian-cve-2026-99059.md) | Oct 24, 2026 | | Linux | perf6.12 amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | perf6.12-debuginfo amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | python3-perf6.12 amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | | Linux | python3-perf6.12-debuginfo amzn 2023 | 1:6.12.113-138.209.amzn2023 | [ALAS2023-2026-3335](https://patchblox.com/security/data/fix/linux/alas2023-2026-3335.md) | Nov 7, 2026 | --- Data as of 2026-11-08T00:53:09Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.