high CVSS 8.1

CVE-2024-36913·Kernel vulnerability

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.

Severity
high
Software
Kernel
Fixed in
6.8.10
Published
2024-05-30

Affected versions

From: 6.7

Until: 6.8.10

Fixed in: 6.8.10

How to fix this CVE

Update your Linux kernel to version 6.8.10 or later to resolve this memory encryption handling vulnerability in the Hyper-V VMBus driver. The patch prevents the freeing of improperly encrypted pages that could expose shared memory, which is critical for confidential computing environments. Systems running kernel versions 6.7 through 6.8.9 should prioritize this update to maintain memory integrity in CoCo VM deployments.

sudo dnf update kernel kernel-devel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Check the installed kernel version with: uname -r
  2. Verify if your system uses Hyper-V/VMBus by checking: grep -i hyperv /proc/cpuinfo or lsmod | grep hv_
  3. Search system logs for memory encryption errors: sudo journalctl -u kernel | grep -i 'set_memory_encrypted\|set_memory_decrypted'
  4. Confirm the patch is applied by checking if kernel version is 6.8.10 or later: uname -r | awk -F. '{if($1>=6 && $2>=8 && $3>=10) print "PATCHED"; else print "VULNERABLE"}'

FAQ

What is CVE-2024-36913?

This vulnerability affects the Linux kernel's Hyper-V VMBus driver and involves improper handling of memory encryption state transitions in confidential computing environments. If memory encryption or decryption operations fail on untrusted hosts, the driver may incorrectly free pages that remain in a shared (decrypted) state, compromising memory isolation guarantees.

Is CVE-2024-36913 being actively exploited?

No, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are currently available. However, its high CVSS score (8.1) reflects the severity of potential memory leakage in CoCo VM environments.

What versions of Kernel are affected by CVE-2024-36913?

Kernel versions 6.7 through 6.8.9 are vulnerable. The fix is available in kernel 6.8.10 and all subsequent releases.

How do I check if my server is vulnerable to CVE-2024-36913?

Run `uname -r` to check your kernel version. If the output shows a version between 6.7 and 6.8.9, and your system uses Hyper-V (check with `lsmod | grep hv_`), then you are vulnerable and should update immediately.

Does Defensia detect CVE-2024-36913?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2024-36913 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2024-42256CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
CVE-2024-36031CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.
CVE-2024-38612CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.
CVE-2024-38623CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni->name' too small (20 vs 256)
CVE-2022-48716CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd938x: fix incorrect used of portid Mixer controls have the channel id in mixer->reg, which is not same as port id. port id should be derived from chan_info array. So fix this. Without this, its possible that we could corrupt struct wcd938x_sdw_priv by accessing port_map array out of range with channel id instead of port id.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-36913. Free for 1 server.

Get started free