CVE-20XX-?

CVE-2026-64046

9.8 CRITICAL 0.5% exploit odds Fix listed Crypto OS & kernel

What it is

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.

At a glance

Exploitability
Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
Exploit odds
0.5% chance of exploitation in the next 30 days (EPSS).
Fix
A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

  1. PublishedDisclosed publicly on CVE.org and NVD
  2. Last updatedMost recent change to the record

Details

Published
Last modified
Exploit probability
0.5% · EPSS, next 30 days
Weakness
CWE-20 · Improper input validation
Record status
Modified

Affected

Attack profile CVSS 3.1 · 9.8

Attack vector
Network
Complexity
Low
Privileges needed
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Raw vector

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

Meme: I wake up, CVE-2026-64046
Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record