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-43336lib/crypto: chacha: Zeroize permuted_state before it leaves scope

Description

In the Linux kernel, the following vulnerability has been resolved: lib/crypto: chacha: Zeroize permuted_state before it leaves scope Since the ChaCha permutation is invertible, the local variable 'permuted_state' is sufficient to compute the original 'state', and thus the key, even after the permutation has been done. While the kernel is quite inconsistent about zeroizing secrets on the stack (and some prominent userspace crypto libraries don't bother at all since it's not guaranteed to work anyway), the kernel does try to do it as a best practice, especially in cases involving the RNG. Thus, explicitly zeroize 'permuted_state' before it goes out of scope.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    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-43336, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVDNVD · Analyzed3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.43% · top 63% of all CVEs (13 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected c08d0e647305c3f8f640010a56c9e4bafb9488d3 – < e90ee961af515a484f091678ce58a4c3f7b73b02
    • affected c08d0e647305c3f8f640010a56c9e4bafb9488d3 – < b416a4245f04a450c67a13e6d96056c37c5b33fe
    • affected c08d0e647305c3f8f640010a56c9e4bafb9488d3 – < bd62d9b44464a6c20a34a74068e7a784d0afa04a
    • affected c08d0e647305c3f8f640010a56c9e4bafb9488d3 – < 066c760acead1fb743bae294dbd89f479ae43b9b
    • affected c08d0e647305c3f8f640010a56c9e4bafb9488d3 – < 1d761e5a7340c46479fb2399598f331e4fe2c633
    • affected c08d0e647305c3f8f640010a56c9e4bafb9488d3 – < 1933249263c3a98df79992f61a566476e4163bcc
    • affected c08d0e647305c3f8f640010a56c9e4bafb9488d3 – < 91999af43ca2125e3b2c18fcfc02912ada02efc3
    • affected c08d0e647305c3f8f640010a56c9e4bafb9488d3 – < e5046823f8fa3677341b541a25af2fcb99a5b1e0
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.169 – ≤ 6.1.*
    • unaffected 6.6.135 – ≤ 6.6.*
    • unaffected 6.12.82 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .