In the Linux kernel, the following vulnerability has been resolved:
hv_netvsc: Don't free decrypted memory
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.
The netvsc driver could free decrypted/shared pages if
set_memory_decrypted() fails. Check the decrypted field in the gpadl
to decide whether to free the memory.
Security readout for executives and security teams
Plain-English summary
A malicious or compromised host may trigger a Linux confidential-computing virtual machine to return shared, decrypted network-driver memory to the normal page allocator. Reuse of that memory could undermine confidentiality, integrity, or availability. The supplied record rates this critical, but the practical risk is concentrated in affected CoCo VMs using the Hyper-V netvsc driver.
Executive priority
Treat as an urgent targeted remediation for confidential-computing workloads, especially where the host is outside the tenant's full trust boundary. Rapidly identify qualifying VMs and obtain fixed kernels from distribution vendors. Broad emergency action across ordinary Linux estates is not supported by the supplied evidence.
Technical view
The hv_netvsc driver mishandled failures from set_memory_decrypted(). When the operation failed but left pages shared, the driver could free those pages because it did not consult the GPADL decrypted state. The stable changes prevent decrypted or shared memory from being returned incorrectly to the allocator. The source bundle lists Linux releases including 5.16, 6.6.31, 6.8.10, and 6.9 as affected.
Likely exposure
Likely exposure is limited to affected Linux kernels running confidential-computing VMs with the Hyper-V netvsc driver and an untrusted or compromised host capable of forcing memory-state conversion failures. Ordinary Linux systems outside this configuration may not be practically exposed. The supplied version data is not sufficiently clear to define complete vulnerable ranges.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not marked as CISA KEV. Exploitation requires influence from the VM host, materially narrowing the threat model while making the issue important for tenants relying on confidential-computing isolation from infrastructure operators. No public exploit evidence is included.
Researcher notes
The key condition is a failed encryption-state transition that nevertheless leaves memory shared. Correct handling depends on the GPADL decrypted flag before freeing pages. The record describes possible functional or security consequences but supplies no demonstrated disclosure, corruption, denial-of-service path, or exploitation evidence. Exact vulnerable version boundaries require vendor confirmation.
Mitigation direction
Install a vendor-supported kernel containing the cited hv_netvsc stable fix.
Prioritize confidential-computing VMs using Hyper-V networking or equivalent netvsc deployments.
Check Linux distribution advisories for exact affected and fixed package versions.
Restrict untrusted host administration and strengthen hypervisor management controls until patched.
Validation and detection
Inventory confidential-computing Linux VMs and identify those loading the hv_netvsc driver.
Record kernel and distribution package versions for each potentially exposed VM.
Confirm the installed kernel includes the applicable cited stable commit or vendor backport.
Review vendor advisories because the supplied affected-version list does not define complete ranges.
Monitor affected VMs for unexplained memory, networking, or stability anomalies.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cve · low confidence lookup
CVE-2024-36911 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
We 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.