CVE-2026-99059

wireguard: noise: reject response consumption after intermediate initiation

  • High 7.7

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.

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.506% likely to be exploited in the next 30 days, higher than 43.816% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.7CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • e7096c131e5161fa3b8e52a650d7719d2857adfd up to but excluding dbd1e21f4301bd2157cd771255f1ca6ba1c8a1f9 (affected)
  • e7096c131e5161fa3b8e52a650d7719d2857adfd up to but excluding f4012ec25a4abb6a23dc40043f61e2d9a7deca6d (affected)
  • e7096c131e5161fa3b8e52a650d7719d2857adfd up to but excluding 6b5b14cb5421e84191e3f6b5a7566783a402ff7f (affected)
  • e7096c131e5161fa3b8e52a650d7719d2857adfd up to but excluding fb5ce4c7790c3eeec820302d08d70ecf46af4295 (affected)
  • e7096c131e5161fa3b8e52a650d7719d2857adfd up to but excluding c76a80db593096edf2b3b3972f58b6342a8c6c04 (affected)
  • e7096c131e5161fa3b8e52a650d7719d2857adfd up to but excluding 4d64a3d6e96aa78619c9c29ffde309794974588a (affected)
  • e7096c131e5161fa3b8e52a650d7719d2857adfd up to but excluding 3bec3d32c2a3afd164fc87f95457df2cf9049c20 (affected)
  • e7096c131e5161fa3b8e52a650d7719d2857adfd up to but excluding d0305f8d90029556260c6824b61c493c424eba9e (affected)
LinuxLinux
  • Default status: affected
  • 5.6 (affected)
  • 0 up to but excluding 5.6 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References