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… (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.
AI Analysis
Technical Summary
The Linux kernel TLS implementation had a vulnerability where the scatterlist API could be given illegal input due to a chain-after-chain condition. When the 'end' pointer was zero but 'start' was not, the code created a wrap link that pointed directly to another chain link, which the scatterlist iterator does not handle recursively. This could cause improper chaining in the crypto processing of TLS data. The patch changes the logic to skip the wrapping link if 'end' is zero, avoiding the chain-after-chain scenario. The fix also reorders wrap chaining steps for logical clarity without functional impact.
Potential Impact
The vulnerability could lead to illegal input being passed to the kernel crypto subsystem during TLS processing, potentially causing errors or unexpected behavior in TLS 1.3 network traffic handling. No known exploits are reported in the wild. The exact impact on confidentiality, integrity, or availability is not detailed in the provided data.
Mitigation Recommendations
A fix has been applied in the Linux kernel to prevent the chain-after-chain condition in the TLS scatterlist handling. Users should update to a Linux kernel version that includes this fix. Since no patch links or specific versions are provided, check the official Linux kernel advisories or vendor updates for the fixed version and apply the update accordingly.
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… (CVE-2026-64046)
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.
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel TLS implementation had a vulnerability where the scatterlist API could be given illegal input due to a chain-after-chain condition. When the 'end' pointer was zero but 'start' was not, the code created a wrap link that pointed directly to another chain link, which the scatterlist iterator does not handle recursively. This could cause improper chaining in the crypto processing of TLS data. The patch changes the logic to skip the wrapping link if 'end' is zero, avoiding the chain-after-chain scenario. The fix also reorders wrap chaining steps for logical clarity without functional impact.
Potential Impact
The vulnerability could lead to illegal input being passed to the kernel crypto subsystem during TLS processing, potentially causing errors or unexpected behavior in TLS 1.3 network traffic handling. No known exploits are reported in the wild. The exact impact on confidentiality, integrity, or availability is not detailed in the provided data.
Mitigation Recommendations
A fix has been applied in the Linux kernel to prevent the chain-after-chain condition in the TLS scatterlist handling. Users should update to a Linux kernel version that includes this fix. Since no patch links or specific versions are provided, check the official Linux kernel advisories or vendor updates for the fixed version and apply the update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3mwm-pxvj-5v4x
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64046"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912cef3
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:56:40 UTC
Last updated: 07/20/2026, 19:41:22 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.