CVE-2026-64046

CVE CVE-2026-64046EUVD EUVD-2026-45619Published 2026-07-19T15:39:31.000ZLast changed 2026-08-05T12:38:38.000ZCVSS 9.8

What the advisory describes

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.

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 9aaaa56845a06aeabdd597cbe19492dc01f281ec <49a5faaa471ddcd37b6893970c9916eb836e7c31; patch: 6.1.175; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <ff26a0e8377dec07e4a7230db7675bed1b9a6d03; patch: 0; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <91359966e247c0244c66d50bbb8e74aefa4321c3; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <acdc12b71c9aa4be5dcd2c8062753c6d2033e235; patch: 7.0.11; patch: 5.15.209; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <af855f4c966afafef74faf8390c7b86568c0d46d; patch: 6.6.142; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <b9c015ef1a7bf1e8dc67f21c6381f36deb2c3a36; patch: 6.18.34; d529d6c9f7e3aaeac13c4948f79799ccb825f29d; patch: 6.12.92; patch: 7.1; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <929b1548e63ac72e104c07d8ee8cbbeeba2fa89a; patch: 5.10.258; 9aaaa56845a06aeabdd597cbe19492dc01f281ec <410351158dfef2d67fea6603680b3a6013c6ed9d; 5.4.14 <5.5; 5.5

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

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

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.