7.1
CWE
908
Advisory Published
Updated

CVE-2024-43815: crypto: mxs-dcp - Ensure payload is zero when using key slot

First published: Sat Aug 17 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: crypto: mxs-dcp - Ensure payload is zero when using key slot We could leak stack memory through the payload field when running AES with a key from one of the hardware's key slots. Fix this by ensuring the payload field is set to 0 in such cases. This does not affect the common use case when the key is supplied from main memory via the descriptor payload.

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Red Hat Kernel-devel
Linux Kernel>=6.10<6.10.3

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2024-43815?

    CVE-2024-43815 has been assigned a moderate severity rating due to the potential leakage of sensitive stack memory.

  • How do I fix CVE-2024-43815?

    To fix CVE-2024-43815, update to the latest version of the Linux kernel that addresses this vulnerability.

  • What software is affected by CVE-2024-43815?

    CVE-2024-43815 affects the Linux kernel versions between 6.10 and 6.10.3.

  • What type of vulnerability is CVE-2024-43815?

    CVE-2024-43815 is a memory exposure vulnerability in the crypto subsystem of the Linux kernel.

  • What are the potential impacts of CVE-2024-43815?

    The potential impact of CVE-2024-43815 includes unauthorized access to sensitive data via leaked stack memory.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203