Skip to content
Threat Brief

← All advisories

CVE-2026-99059

High 7.7No known exploitationFix available

wireguard: noise: reject response consumption after intermediate initiation

Record last updated

CVSS score

7.7

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 44% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom e7096c131e5161fa3b8e52a650d7719d2857adfd before d0305f8d90029556260c6824b61c493c424eba9ed0305f8d90029556260c6824b61c493c424eba9eCVE Program
LinuxLinuxfrom e7096c131e5161fa3b8e52a650d7719d2857adfd before c76a80db593096edf2b3b3972f58b6342a8c6c04c76a80db593096edf2b3b3972f58b6342a8c6c04CVE Program
LinuxLinuxfrom e7096c131e5161fa3b8e52a650d7719d2857adfd before 4d64a3d6e96aa78619c9c29ffde309794974588a4d64a3d6e96aa78619c9c29ffde309794974588aCVE Program
LinuxLinuxfrom e7096c131e5161fa3b8e52a650d7719d2857adfd before 3bec3d32c2a3afd164fc87f95457df2cf9049c203bec3d32c2a3afd164fc87f95457df2cf9049c20CVE Program
LinuxLinuxfrom e7096c131e5161fa3b8e52a650d7719d2857adfd before dbd1e21f4301bd2157cd771255f1ca6ba1c8a1f9dbd1e21f4301bd2157cd771255f1ca6ba1c8a1f9CVE Program
LinuxLinuxfrom e7096c131e5161fa3b8e52a650d7719d2857adfd before f4012ec25a4abb6a23dc40043f61e2d9a7deca6df4012ec25a4abb6a23dc40043f61e2d9a7deca6dCVE Program
LinuxLinuxfrom e7096c131e5161fa3b8e52a650d7719d2857adfd before 6b5b14cb5421e84191e3f6b5a7566783a402ff7f6b5b14cb5421e84191e3f6b5a7566783a402ff7fCVE Program
LinuxLinuxfrom e7096c131e5161fa3b8e52a650d7719d2857adfd before fb5ce4c7790c3eeec820302d08d70ecf46af4295fb5ce4c7790c3eeec820302d08d70ecf46af4295CVE Program
LinuxLinux5.6Not documentedCVE Program
Microsoftazl3 kernel 6.6.157.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 kernel 6.6.159.1-1 on Azure Linux 3.0Not documented6.6.161.1-1Microsoft MSRC
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 5.10.273 up to and including 5.10.*Not documentedCVE Program
LinuxLinux (unaffected)from 5.15.224 up to and including 5.15.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.1.191 up to and including 6.1.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.113 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.57 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.6.160 up to and including 6.6.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.11 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 5.6Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Advisory change

    Microsoft advisory revised (6.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  8. Advisory change

    Microsoft advisory revised (7.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  9. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references

CVE-2026-99059: wireguard: noise: reject response consumption after intermediate initiation · Threat Brief