Cyber Resilience

CVE-2024-36353

Published
02 March 2025
Modified
15 April 2026
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS Score 0.0016 5th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2024-36353 is a medium-severity Incomplete Cleanup (CWE-459) vulnerability in Amd (inferred from references). Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-14 (Non-persistence) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Insufficient clearing of GPU global memory could allow a malicious process running on the same GPU to read left over memory values potentially leading to loss of confidentiality.

CWE(s)
CWE-459

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-66675Shared CWE-459
CVE-2025-2260Shared CWE-459
CVE-2023-31356Shared CWE-459
CVE-2025-60730Shared CWE-459
CVE-2024-50385Shared CWE-459
CVE-2023-41835Shared CWE-459
CVE-2024-53869Shared CWE-459
CVE-2025-55910Shared CWE-459
CVE-2024-26841Shared CWE-459
CVE-2024-47728Shared CWE-459

Affected Assets

Amd
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V6.4.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover incomplete cleanup through dynamic analysis or resource-leak testing.

SI-14 Non-persistence good match

Non-persistence mechanisms explicitly initiate resources in a known state and terminate them, directly enforcing cleanup.

AC-12 Session Termination partial match

Session termination forces explicit release of session-related temporary resources.

SC-4 Information in Shared System Resources partial match

Preventing unintended information transfer through shared resources requires complete cleanup of those resources.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-development practices and coding standards normally require proper resource release and cleanup.

ID.AM-08 partial match
prevents

Life-cycle management encompasses disposal of temporary resources but does not specifically target runtime cleanup bugs.

PR.DS-10 partial match
prevents

Explicitly calls for removing sensitive data after use, directly addressing one class of incomplete cleanup.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.10 Information deletion full match
degrades

Explicitly requires secure deletion of temporary or residual data, directly addressing incomplete cleanup.

A.8.25 Secure development life cycle partial match
prevents

SDLC practices include cleanup steps, yet the weakness can still occur if those steps are omitted.

A.8.28 Secure coding partial match
prevents

Secure-coding rules can mandate explicit cleanup of temporary resources, but do not guarantee it.

A.8.32 Change management partial match
finds

Change-management processes may require cleanup verification, but the control itself does not address the weakness.

References