CVE-2026-43336

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. CVE-2026-43336
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.

7.5 /10

CVSS v3 : HIGH

V3 Legend

Vector :

Exploitability : 3.9 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact NONE

Availability Impact NONE

Scope UNCHANGED

References
Link Resource
https://git.kernel.org/stable/c/066c760acead1fb743bae294dbd89f479ae43b9b Patch
https://git.kernel.org/stable/c/1933249263c3a98df79992f61a566476e4163bcc Patch
https://git.kernel.org/stable/c/1d761e5a7340c46479fb2399598f331e4fe2c633 Patch
https://git.kernel.org/stable/c/91999af43ca2125e3b2c18fcfc02912ada02efc3 Patch
https://git.kernel.org/stable/c/b416a4245f04a450c67a13e6d96056c37c5b33fe Patch
https://git.kernel.org/stable/c/bd62d9b44464a6c20a34a74068e7a784d0afa04a Patch
https://git.kernel.org/stable/c/e5046823f8fa3677341b541a25af2fcb99a5b1e0 Patch
https://git.kernel.org/stable/c/e90ee961af515a484f091678ce58a4c3f7b73b02 Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
History

11 Nov 2026, 20:10

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta: lib/crypto: chacha: Poner a cero permuted_state antes de que salga de su ámbito Dado que la permutación ChaCha es invertible, la variable local ’permuted_state’ es suficiente para calcular el ’state’ original, y por lo tanto la clave, incluso después de que se haya realizado la permutación. Aunque el kernel es bastante inconsistente en cuanto a poner a cero secretos en la pila (y algunas bibliotecas criptográficas prominentes del espacio de usuario no se molestan en absoluto ya que de todos modos no se garantiza que funcione), el kernel sí intenta hacerlo como una buena práctica, especialmente en casos que involucran al RNG. Por lo tanto, poner a cero explícitamente ’permuted_state’ antes de que quede fuera de su ámbito.
Information

Published : 2026-05-08 14:16

Updated : 2026-11-11 20:10

NVD link : CVE-2026-43336

Mitre link : CVE-2026-43336

CVE.ORG link : CVE-2026-43336

JSON object : View

Products Affected

linux

  • linux_kernel
CWE
NVD-CWE-noinfo