Linux: Exposure of Sensitive System Information Due to Uncleared Debug Information
CVE-2024-36912 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.6 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions 1999644d95194d4a58d3e80ad04ce19220a01a81, 8e62341f5c45b27519b7d193bcc32ada416ad9d8, bfae56be077ba14311509e70706a13458f87ea99 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.97% chance of exploitation within 30 days, higher than 62% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Linux to 1999644d95194d4a58d3e80ad04ce19220a01a81 or 8e62341f5c45b27519b7d193bcc32ada416ad9d8 or bfae56be077ba14311509e70706a13458f87ea99 or 211f514ebf1ef5de37b1cf6df9d28a56cfd242ca, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.1.91 or 6.6.31 or 6.8.10, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | d4dccf353db80e209f262e3973c834e6e48ba9a9 up to, but not including, 1999644d95194d4a58d3e80ad04ce19220a01a81; d4dccf353db80e209f262e3973c834e6e48ba9a9 up to, but not including, 8e62341f5c45b27519b7d193bcc32ada416ad9d8; d4dccf353db80e209f262e3973c834e6e48ba9a9 up to, but not including, bfae56be077ba14311509e70706a13458f87ea99; d4dccf353db80e209f262e3973c834e6e48ba9a9 up to, but not including, 211f514ebf1ef5de37b1cf6df9d28a56cfd242ca; 5.16 | 1999644d95194d4a58d3e80ad04ce19220a01a81, 8e62341f5c45b27519b7d193bcc32ada416ad9d8, bfae56be077ba14311509e70706a13458f87ea99, 211f514ebf1ef5de37b1cf6df9d28a56cfd242ca |
| Linux | Linux Kernel | 5.16 up to, but not including, 6.1.91; 6.2 up to, but not including, 6.6.31; 6.7 up to, but not including, 6.8.10; 6.9 | 6.1.91, 6.6.31, 6.8.10 |
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
- AdjacentThe attacker must be on the same local network segment.
- 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:A/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.6 | 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: Track decrypted status in vmbus_gpadl 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. In order to make sure callers of vmbus_establish_gpadl() and vmbus_teardown_gpadl() don't return decrypted/shared pages to allocators, add a field in struct vmbus_gpadl to keep track of the decryption status of the buffers. This will allow the callers to know if they should free or leak the pages.
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
Recent Exposure of Sensitive System Information Due to Uncleared Debug Information vulnerabilities
- 9.3 Critical severity
- 7.5 High severity
Spotted an error? Tell us.