CVE-2026-64047net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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).
- CVSS
- 9.8 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 9aaaa56845a06aeabdd597cbe19492dc01f281ec before 73963a375885d5ccb7def39fd0b4f542e0f343dd; from 9aaaa56845a06aeabdd597cbe19492dc01f281ec before 47110c3a9ac247b688657337f5981efcfcb240dc; from 9aaaa56845a06aeabdd597cbe19492dc01f281ec before 84158c2997159df4a0d70cd9c46774512d32a522; from 9aaaa56845a06aeabdd597cbe19492dc01f281ec before 131ef12057d92b77b636321b7849c69222405a97; from 9aaaa56845a06aeabdd597cbe19492dc01f281ec before 66339b71f105e6f83e0da3b9583d95077534fe1d; from 9aaaa56845a06aeabdd597cbe19492dc01f281ec before eca989eab4b2599dcb02f72140a7c08f08838520; 9aaaa56845a06aeabdd597cbe19492dc01f281ec builds before 2fb0dc7e0099686c4e9d2732745d8a31b18c3628; from 9aaaa56845a06aeabdd597cbe19492dc01f281ec before 285943c6e7ca309bbea84b253745154241d9788a; and 2 more ranges | CNA record |
linux linux_kernel linux:linux_kernel | from 5.4.14 before 5.5; from 5.5.1 before 5.10.258; from 5.11 before 5.15.209; from 5.16 before 6.1.175; from 6.2 before 6.6.142; from 6.7 before 6.12.92; from 6.13 before 6.18.34; from 6.19 before 7.0.11; and 5 more ranges | NVD |
References
- https://git.kernel.org/stable/c/73963a375885d5ccb7def39fd0b4f542e0f343ddpatch
- https://git.kernel.org/stable/c/47110c3a9ac247b688657337f5981efcfcb240dcpatch
- https://git.kernel.org/stable/c/84158c2997159df4a0d70cd9c46774512d32a522patch
- https://git.kernel.org/stable/c/131ef12057d92b77b636321b7849c69222405a97patch
- https://git.kernel.org/stable/c/66339b71f105e6f83e0da3b9583d95077534fe1dpatch
- https://git.kernel.org/stable/c/eca989eab4b2599dcb02f72140a7c08f08838520patch
- https://git.kernel.org/stable/c/2fb0dc7e0099686c4e9d2732745d8a31b18c3628patch
- https://git.kernel.org/stable/c/285943c6e7ca309bbea84b253745154241d9788apatch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.