CVE-2024-36910: uio_hv_generic: Don't free decrypted memory

Published May 30, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

uiohvgeneric: Don't free decrypted memory

In CoCo VMs it is possible for the untrusted host to cause setmemoryencrypted() or setmemorydecrypted() 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 VMBus device UIO driver could free decrypted/shared pages if setmemorydecrypted() fails. Check the decrypted field in the gpadl to decide whether to free the memory.

Affected Software

9 affected componentsFixes available
Linux Linux kernel<6.1.91
Linux Linux kernel>=6.2<6.6.31
Linux Linux kernel>=6.7<6.8.10
Linux Linux kernel=6.9-rc1
Linux Linux kernel=6.9-rc2
Linux Linux kernel=6.9-rc3
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.22-16.12.25-1
Microsoft azl3 kernel 6.6.78.1-3
Microsoft azl3 kernel 6.6.64.2-9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1
  2. Configuration

    Update uio_hv_generic so it checks whether the memory remains decrypted/shared via the gpadl "decrypted" field; only free memory when the gpadl indicates it is not decrypted. Specifically, ensure the driver does not free decrypted/shared pages if set_memory_encrypted() or set_memory_decrypted() returns an error.

    uio_hv_generic (VMBus device UIO driver) free logic for decrypted/shared pages = Do not free decrypted/shared memory when set_memory_encrypted() or set_memory_decrypted() fails

Event History

May 30, 2024
CVE Published
via MITRE·03:29 PM
Data Sourced
via MITRE·03:29 PM
DescriptionSeverity
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 8, 2024
Data Sourced
via Launchpad·11:25 PM
Description
Apr 9, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Apr 27, 2025
Data Sourced
via Ubuntu·12:27 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-36910?

CVE-2024-36910 has a severity rating that indicates it poses a security risk to the Linux kernel.

2

How do I fix CVE-2024-36910?

To fix CVE-2024-36910, upgrade to the patched versions of the Linux kernel: 6.1.123-1, 6.1.128-1, 6.12.12-1, or 6.12.16-1.

3

Which versions of Linux are affected by CVE-2024-36910?

CVE-2024-36910 affects Linux kernel versions up to 5.10.234-1.

4

What types of systems are impacted by CVE-2024-36910?

CVE-2024-36910 impacts systems running the Linux kernel, especially those in CoCo virtual machines.

5

Is CVE-2024-36910 a local or remote vulnerability?

CVE-2024-36910 is a local vulnerability that an untrusted host can exploit.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203