CVE-2024-36913
Linux Kernel 5.16 – 6.1.143
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-36913 is a critical-severity Exposure of Sensitive System Information Due to Uncleared Debug Information (CWE-1258) vulnerability in Linux Linux Kernel. Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 48th 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 CM-7 (Least Functionality) and SA-3 (System Development Life Cycle) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-36264
Vulnerability Data
In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is…
more
returned and the resulting memory is shared. Callers need to take care to handle these errors to avoid returning decrypted (shared) memory to the page allocator, which could lead to functional or security issues. VMBus code could free decrypted pages if set_memory_encrypted()/decrypted() fails. Leak the pages if this happens.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V13.3.3V17.2.1V11.2.1
Mitigating Controls (NIST 800-53 r5) AI
Disabling debug and other non-essential functionality prevents the system from entering a debug state that would expose uncleared sensitive values.
Mandating a security-aware SDLC ensures hardware designs incorporate debug-mode clearing requirements.
Acquisition requirements can explicitly mandate secure debug behavior and data clearing in supplied hardware.
Requiring security engineering principles during design directly addresses the need to clear sensitive data on debug entry.
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.
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.
Security testing in development can detect uncleared debug information before release.
Cryptographic key management and secure handling requirements reduce exposure of sensitive values during debug entry.
Secure system architecture and engineering principles directly address clearing of sensitive data on debug transitions.
Secure coding practices can mandate explicit clearing of debug registers and memory.
Test information protection includes ensuring debug artifacts do not leak sensitive data.