CVE-2026-64046: 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 ...

Description

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.

Metrics

CVSS 3.1

9.8/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Probability

0.51%

40.9th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec, < 49a5faaa471ddcd37b6893970c9916eb836e7c31; >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec, < 91359966e247c0244c66d50bbb8e74aefa4321c3; >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec, < 410351158dfef2d67fea6603680b3a6013c6ed9d; >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec, < acdc12b71c9aa4be5dcd2c8062753c6d2033e235; >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec, < 929b1548e63ac72e104c07d8ee8cbbeeba2fa89a; >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec, < af855f4c966afafef74faf8390c7b86568c0d46d; >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec, < b9c015ef1a7bf1e8dc67f21c6381f36deb2c3a36; >= 9aaaa56845a06aeabdd597cbe19492dc01f281ec, < ff26a0e8377dec07e4a7230db7675bed1b9a6d03; d529d6c9f7e3aaeac13c4948f79799ccb825f29d; >= 5.4.14, < 5.5
Linux	Linux	5.5

References

Timeline

Published: Jul 19, 2026
Last Modified: Jul 30, 2026
Status: Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-64046?

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.

How severe is CVE-2026-64046?

CVE-2026-64046 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 0.51% probability of exploitation in the next 30 days.

How do I fix CVE-2026-64046?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →