Security readout for executives and security teams
Plain-English summary
A malicious or compromised host may cause memory-encryption transitions to fail inside a Linux confidential-computing virtual machine. The guest could then return shared, decrypted memory to its allocator, risking exposure, corruption, or disruption. The issue matters primarily where Linux confidential VMs use Hyper-V VMBus; ordinary Linux deployments are not shown as exposed by these sources.
Executive priority
Treat as urgent for confidential Linux workloads on potentially untrusted Hyper-V hosts because the stated impact spans confidentiality, integrity, and availability. Use normal priority for systems outside that architecture after confirming they are not exposed. Obtain distribution-specific update guidance promptly; the supplied version matrix is insufficient for precise fleet-wide patch decisions.
Technical view
In CoCo guests, an untrusted host can induce failures in set_memory_encrypted() or set_memory_decrypted(), leaving VMBus GPADL buffers shared. Callers could mistakenly release those pages to the allocator. The kernel fixes track buffer decryption state in struct vmbus_gpadl, allowing callers to avoid freeing pages that remain shared.
Likely exposure
Prioritize Linux confidential-computing VMs using Hyper-V VMBus, especially where the host is outside the guest owner's trust boundary. The bundle marks versions 5.16, 0, 6.1.91, 6.6.31, 6.8.10, and 6.9 as affected, but its unusual version data requires validation against distribution advisories and kernel provenance.
Exploitation context
The supplied CVSS is 9.6 and describes adjacent access with no privileges or user interaction. Exploitation depends on an untrusted host influencing a confidential VM's memory-state transitions. The bundle says this CVE is not in KEV, and no supplied source establishes active exploitation or a public exploit.
Researcher notes
CWE-1258 fits exposure of sensitive memory caused by incorrect handling of a failed state transition. The upstream remediation favors leaking pages that remain shared over returning them to an allocator. The bundle provides four stable-kernel commits but no distribution mappings, exploit evidence, or detailed affected-configuration matrix; conclusions beyond CoCo, VMBus, and host influence would be speculative.
Mitigation direction
- Identify confidential Linux VMs using Hyper-V VMBus and prioritize them for review.
- Apply a vendor-supported kernel update containing the applicable referenced stable fix.
- Confirm distribution backport status rather than relying only on the reported upstream version numbers.
- Until updated, reconsider sensitive confidential workloads running on hosts outside your trust boundary.
Validation and detection
- Record each guest's kernel version, distribution build, virtualization platform, and confidential-computing mode.
- Verify the installed kernel includes the applicable fix or an equivalent vendor backport.
- Confirm exposed workloads actually use Hyper-V VMBus GPADL functionality.
- After updating, run vendor-approved regression tests for VMBus devices and confidential-memory handling.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1258: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-36912 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H2.86LinuxCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/1999644d95194d4a58d3e80ad04ce19220a01a81CVE reference, Linux
- https://git.kernel.org/stable/c/8e62341f5c45b27519b7d193bcc32ada416ad9d8CVE reference, Linux
- https://git.kernel.org/stable/c/bfae56be077ba14311509e70706a13458f87ea99CVE reference, Linux
- https://git.kernel.org/stable/c/211f514ebf1ef5de37b1cf6df9d28a56cfd242caCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive System Information Due to Uncleared Debug Information
Exposure of Sensitive System Information Due to Uncleared Debug Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.