CVE-2026-64047

CVE CVE-2026-64047EUVD EUVD-2026-45620Published 2026-07-19T15:39:31.000ZLast changed 2026-08-05T12:38:39.000ZCVSS 9.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring When an sk_msg scatterlist ring wraps (sg.end < sg.start), tls_push_record() chains the tail portion of the ring to the head using sg_chain(). An extra entry in the sg array is reserved for this: struct sk_msg_sg { [...] /* The extra two elements: * 1) used for chaining the front and sections when the list becomes * partitioned (e.g. end < start). The crypto APIs require the * chaining; * 2) to chain tailer SG entries after the message. */ struct scatterlist data[MAX_MSG_FRAGS + 2]; The current code uses MAX_SKB_FRAGS + 1 as the ring size: sg_chain(&msg_pl->sg.data[msg_pl->sg.start], MAX_SKB_FRAGS - msg_pl->sg.start + 1, msg_pl->sg.data); This places the chain pointer at sg_chain(data[start], (MAX_SKB_FRAGS - msg_start + 1) .. = &data[start] + (MAX_SKB_FRAGS - msg_start + 1) - 1 = data[start + (MAX_SKB_FRAGS - start + 1) - 1] = data[MAX_SKB_FRAGS] instead of the true last entry. This is likely due to a "race" of the commit under Fixes landing close to commit 031097d9e079 ("bpf: sk_msg, zap ingress queue on psock down") Convert to ARRAY_SIZE and drop the data[start] / - start (as suggested by Sabrina).

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 5.5; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <66339b71f105e6f83e0da3b9583d95077534fe1d; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <eca989eab4b2599dcb02f72140a7c08f08838520; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <2fb0dc7e0099686c4e9d2732745d8a31b18c3628; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <285943c6e7ca309bbea84b253745154241d9788a; patch: 0; patch: 7.0.11; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <131ef12057d92b77b636321b7849c69222405a97; patch: 6.12.92; patch: 5.15.209; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <73963a375885d5ccb7def39fd0b4f542e0f343dd; patch: 6.18.34; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <47110c3a9ac247b688657337f5981efcfcb240dc; patch: 6.6.142; patch: 5.10.258; patch: 6.1.175; patch: 7.1; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <84158c2997159df4a0d70cd9c46774512d32a522; 5.4.14 <5.5; d529d6c9f7e3aaeac13c4948f79799ccb825f29d

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.