Skip to contentSkip to conversation

go: fix CVE-2026-56862

PATCH New Benhur Tessele 1 participant 1 message Oct 16

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 go: fix CVE-2026-56862

A malicious TLS 1.3 peer could keep sending KeyUpdate messages after the handshake completed, forcing the other side to perform key derivation indefinitely, because handshake records were always treated as state-advancing.

Backport the upstream fix [1]. The bogo_config.json hunk is dropped since the BoGo test harness does not exist in Go 1.22, and the new test is adapted to use testConfig.

[1] https://github.com/golang/go/commit/27420571845abc6a97e19e21542a3213a74f67f4

---
 meta/recipes-devtools/go/go-1.22.12.inc       |  1 +
 .../go/go/CVE-2026-56862.patch                | 98 +++++++++++++++++++
 2 files changed, 99 insertions(+)
 create mode 100644 meta/recipes-devtools/go/go/CVE-2026-56862.patch
meta/recipes-devtools/go/go-1.22.12.inc +1 -0
index c8fb9ef450..cec3bbbb4e 100644
@@ -63,6 +63,7 @@ SRC_URI += "\
     file://CVE-2026-32288.patch \
     file://CVE-2026-27145.patch \
     file://CVE-2026-39823.patch \
+    file://CVE-2026-56862.patch \
 "
 SRC_URI[main.sha256sum] = "012a7e1f37f362c0918c1dfa3334458ac2da1628c4b9cf4d9ca02db986e17d71"
 
meta/recipes-devtools/go/go/CVE-2026-56862.patch new file +98 -0

98 lines not on this page · raw message