Vulnary
← back to the feed
Critical· 9.6official fix available

CVE-2024-36912

The vulnerability in the Linux kernel's Hyper-V VMBus driver could allow an untrusted host to cause memory decryption failures, potentially returning decrypted memory to the page allocator and leading to security issues. It has been resolved by adding a decryption status track in the vmbus_gpadl structure. Users should apply the kernel patch to mitigate the risk.

publishedMay 30, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.6
critical · how bad it is
exploitation · epss
<1%
57th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 4, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel users, particularly those running CoCo VMs with Hyper-V VMBus.

02

Real-world impact

An attacker could cause the system to mishandle memory, leading to possible data exposure, corruption, or denial of service.

03

Why this severity

CVSS v3.1 base score 9.6 (Critical) due to attack vector being adjacent network, low complexity, no privileges or user interaction required, with high impacts to confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 01Obtain the Linux kernel patch that addresses CVE-2024-36912 from the vendor.
  2. 02Apply the patch to the affected kernel version.
  3. 03Reboot the system to load the patched kernel.

NVD-referenced vendor advisory (NVD description states the vulnerability has been resolved)

05

Timeline

  1. May 30, 2024 · May 30, 2024
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 5, 2026 · 1d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorAdjacent network
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeChanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →