Improper Cross-boundary Removal of Sensitive Data Affecting python3-perf-debuginfo package, versions <1:6.1.170-210.320.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.05% (15th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-PYTHON3PERFDEBUGINFO-16737784
  • published18 May 2026
  • disclosed8 May 2026

Introduced: 8 May 2026

NewCVE-2026-43336  (opens in a new tab)
CWE-212  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 python3-perf-debuginfo to version 1:6.1.170-210.320.amzn2023 or higher.
This issue was patched in ALAS2023-2026-1694.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3-perf-debuginfo package and not the python3-perf-debuginfo package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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.