Linux: Exposure of Sensitive System Information Due to Uncleared Debug Information
CVE-2024-36913 is a critical-severity exposure of sensitive system information due to uncleared debug information vulnerability in Linux, with a CVSS 3.1 base score of 9.3 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists versions 7f2afcbfe4f6b6047b5f68db5067b7321e5be125, 6123a4e8e25bd40cf44db14694abac00e6b664e6, e813a0fc2e597146e9cebea61ced9c796d4e308f as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.66% chance of exploitation within 30 days, higher than 52% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Linux to 7f2afcbfe4f6b6047b5f68db5067b7321e5be125 or 6123a4e8e25bd40cf44db14694abac00e6b664e6 or e813a0fc2e597146e9cebea61ced9c796d4e308f or 03f5a999adba062456c8c818a683beb1b498983a, whichever matches your release line, or a later version.
- Update linux_kernel to 6123a4e8e25b or e813a0fc2e59 or 03f5a999adba, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | f2f136c05fb6093818a3b3fefcba46231ac66a62 up to, but not including, 7f2afcbfe4f6b6047b5f68db5067b7321e5be125; f2f136c05fb6093818a3b3fefcba46231ac66a62 up to, but not including, 6123a4e8e25bd40cf44db14694abac00e6b664e6; f2f136c05fb6093818a3b3fefcba46231ac66a62 up to, but not including, e813a0fc2e597146e9cebea61ced9c796d4e308f; f2f136c05fb6093818a3b3fefcba46231ac66a62 up to, but not including, 03f5a999adba062456c8c818a683beb1b498983a; 5.16 | 7f2afcbfe4f6b6047b5f68db5067b7321e5be125, 6123a4e8e25bd40cf44db14694abac00e6b664e6, e813a0fc2e597146e9cebea61ced9c796d4e308f, 03f5a999adba062456c8c818a683beb1b498983a |
| Linux | linux_kernel | 1da177e4c3f4 up to, but not including, 6123a4e8e25b; 1da177e4c3f4 up to, but not including, e813a0fc2e59; 1da177e4c3f4 up to, but not including, 03f5a999adba | 6123a4e8e25b, e813a0fc2e59, 03f5a999adba |
| Debian | Debian Linux | 11.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.3 | Critical | CNA |
| CVSS 3.1 | 8.1 | High | CISA (ADP) |
Official description
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 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Exposure of Sensitive System Information Due to Uncleared Debug Information
The hardware product enters debug mode but does not fully clear security-sensitive values, such as keys and intermediate values in cryptographic operations.
How developers prevent this class of flaw
- Whenever debug mode is enabled, all registers containing sensitive assets must be cleared.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Third-party and government advisories
- lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlMailing List, Third Party Advisory
Recent Exposure of Sensitive System Information Due to Uncleared Debug Information vulnerabilities
- 9.6 Critical severity
- 7.5 High severity
Spotted an error? Tell us.