CVE-2026-64046: Linux Kernel

Critical severity, CVSS 9.8. EPSS: 0.8% chance of exploitation in the next 30 days.

In the Linux kernel, the following vulnerability has been resolved: net: tls: prevent chain-after-chain in plain text SG Sashiko points out that if end = 0 (start != 0) the current code will create a chain link to content type right after the wrap link: This would create a chain where the wrap link points directly to another chain link. The scatterlist API sg_next iterator does not recursively resolve consecutive chain links. meaning this is illegal input to crypto. The wrapping link is unnecessary if end = 0. end is the entry after the last one used so end = 0 means there's nothing pushed after the wrap: end start i v v v [ ]...[ ][ d ][ d ][ d ][ d ][rsv for wrap] Skip the wrapping in this case. TLS 1.3 can use the "wrapping slot" for it's chaining if end = 0. This avoids the chain-after-chain. Move the wrap chaining before marking END and chaining off content type, that feels like more logical ordering to me, but should not matter from functional perspective.

Affected products

• Linux Linux Kernel: from 5.4.14, before 5.5 (fixed in 5.5); from 5.5.1, before 5.10.258 (fixed in 5.10.258); from 5.11, before 5.15.209 (fixed in 5.15.209); from 5.16, before 6.1.175 (fixed in 6.1.175); from 6.2, before 6.6.142 (fixed in 6.6.142); from 6.7, before 6.12.92 (fixed in 6.12.92); …

Published 2026-07-19. Last modified 2026-09-02.