Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64046net: tls: prevent chain-after-chain in plain text SG

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64046, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.51% · top 56% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 9aaaa56845a06aeabdd597cbe19492dc01f281ec – < 49a5faaa471ddcd37b6893970c9916eb836e7c31
    • affected 9aaaa56845a06aeabdd597cbe19492dc01f281ec – < 91359966e247c0244c66d50bbb8e74aefa4321c3
    • affected 9aaaa56845a06aeabdd597cbe19492dc01f281ec – < 410351158dfef2d67fea6603680b3a6013c6ed9d
    • affected 9aaaa56845a06aeabdd597cbe19492dc01f281ec – < acdc12b71c9aa4be5dcd2c8062753c6d2033e235
    • affected 9aaaa56845a06aeabdd597cbe19492dc01f281ec – < 929b1548e63ac72e104c07d8ee8cbbeeba2fa89a
    • affected 9aaaa56845a06aeabdd597cbe19492dc01f281ec – < af855f4c966afafef74faf8390c7b86568c0d46d
    • affected 9aaaa56845a06aeabdd597cbe19492dc01f281ec – < b9c015ef1a7bf1e8dc67f21c6381f36deb2c3a36
    • affected 9aaaa56845a06aeabdd597cbe19492dc01f281ec – < ff26a0e8377dec07e4a7230db7675bed1b9a6d03
    • affected d529d6c9f7e3aaeac13c4948f79799ccb825f29d
    • affected 5.4.14 – < 5.5
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.142 – ≤ 6.6.*
    • unaffected 6.12.92 – ≤ 6.12.*
    • unaffected 6.18.34 – ≤ 6.18.*
    • unaffected 7.0.11 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64046 badge
[![CVE-2026-64046](https://cveledger.app/badge/CVE-2026-64046.svg)](https://cveledger.app/cve/CVE-2026-64046)

Record last updated .