CVE-2024-36909: Drivers: hv: vmbus: Don't free ring buffers that couldn't be re-encrypted

Published May 30, 2024
·
Updated

Drivers: hv: vmbus: Don't free ring buffers that couldn't be re-encrypted

Affected Software

8 affected componentsFixes available
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.25-16.12.27-1
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
Microsoft cbl2 kernel 5.15.186.1-1

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.25-1Fixed in 6.12.27-1
  2. Configuration

    Modify the VMBus ring buffer code to check the decrypted field in the struct vmbus_gpadl for the ring buffers; use this to decide whether to free the memory, so decrypted/shared pages are not returned to the page allocator.

    Linux kernel hv vmbus ring buffer / GPADL handling vmbus_gpadl.decrypted check before freeing = Only free ring buffer memory when decrypted field indicates it is safe (i.e., do not free decrypted/shared pages)
  3. Compensating control

    In CoCo VMs, assume the untrusted host may cause set_memory_encrypted() or set_memory_decrypted() to fail; ensure error handling prevents decrypted/shared memory from being freed/returned to the page allocator.

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
Description
Data Sourced
via NVD·04:15 PM
RemedySeverityWeaknessAffected Software
Aug 8, 2024
Data Sourced
via Launchpad·11:25 PM
Description
Apr 27, 2025
Data Sourced
via Ubuntu·12:27 AM
RemedyDescriptionSeverityAffected Software
Oct 2, 2025
Data Sourced
via Microsoft·01:06 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·01:06 AM
Affected Software
Updated
via Microsoft·01:06 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2024-36909?

CVE-2024-36909 has a severity rating that indicates a potential risk due to improper memory management in the Linux kernel.

2

How do I fix CVE-2024-36909?

To fix CVE-2024-36909, upgrade to the patched versions of the Linux package, specifically 6.1.123-1, 6.1.128-1, 6.12.12-1, or 6.12.13-1.

3

Which Linux kernel versions are affected by CVE-2024-36909?

CVE-2024-36909 affects Linux kernel versions up to and including 5.10.226-1.

4

Is CVE-2024-36909 specific to any Linux distributions?

Yes, CVE-2024-36909 is particularly noted within the Debian distribution's Linux kernel packages.

5

What type of vulnerability is CVE-2024-36909?

CVE-2024-36909 is a memory management vulnerability related to drivers in the Linux kernel.

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