VULNOS
All Threat Alerts
criticalCVE Alert
CVE-2024-36913

Critical Vulnerability: CVE-2024-36913 — debian, linux — debian_linux, linux_kernel

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 coul

Sunday, September 27, 2026debianVulnios Threat Intelligence
Share:

Vulnerability Snapshot

CVE-2024-36913 is rated CRITICAL — exploitation is trivial or already observed in the wild and impact is severe. Patch immediately, not on the next maintenance window.

Affected technology: debian_linux, linux_kernel.

Executive Summary

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.

Why It Matters

CVE-2024-36913 is rated CRITICAL severity, requiring immediate attention from security teams.

CVSS Base Score: 9.3/10

Affected Technologies

Vendors: debian, linux

Products: debian_linux, linux_kernel

🛡️What Defenders Should Check

  • Check if you are affected — Review your asset inventory for products listed in CVE-2024-36913.
  • Apply available patches — Visit vendor advisories for the latest security updates.
  • Monitor for exploitation — Check your SIEM/IDS logs for related indicators.

    • Use Vulnios to continuously monitor your exposure to CVE-2024-36913 and similar vulnerabilities.

    References & Sources

  • https://git.kernel.org/stable/c/03f5a999adba062456c8c818a683beb1b498983a
  • https://git.kernel.org/stable/c/6123a4e8e25bd40cf44db14694abac00e6b664e6
  • https://git.kernel.org/stable/c/7f2afcbfe4f6b6047b5f68db5067b7321e5be125
  • https://git.kernel.org/stable/c/e813a0fc2e597146e9cebea61ced9c796d4e308f
  • https://git.kernel.org/stable/c/03f5a999adba062456c8c818a683beb1b498983a
  • https://git.kernel.org/stable/c/6123a4e8e25bd40cf44db14694abac00e6b664e6
  • https://git.kernel.org/stable/c/e813a0fc2e597146e9cebea61ced9c796d4e308f
  • https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html

    • How Vulnios Detects This

    Vulnios scans for this vulnerability using Trivy and Grype for CVE matching against your container images and OS package manifests. Run a scan against your environment to see whether you are exposed; findings are linked back to the original CVE record so triage starts with the patch path already known.

    AI Security Advisor

    Powered by Gemini

    Get AI-powered security recommendations tailored to this specific threat — including risk assessment, detection guidance, MITRE ATT&CK mapping, and actionable remediation steps.

    Affected Products

    debian_linuxlinux_kernel

    Sources

    Related Threat Alerts

    Frequently Asked Questions

    What is CVE-2024-36913?

    CVE-2024-36913 is a critical-severity vulnerability tracked under the Common Vulnerabilities and Exposures program. 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_memo

    Am I affected?

    Check whether your environment runs debian_linux, linux_kernel. If you operate any of those, treat yourself as in scope until you have evidence otherwise. A Vulnios scan will identify the exact assets carrying the affected version.

    How urgent is the response?

    Critical: do not wait for your normal patch cycle. Verify exposure today, apply the vendor patch immediately, and add detection rules for any post-exploit indicators.

    How do I remediate?

    Apply the vendor patch listed in the upstream advisory linked under Sources. If the patch is not yet available, follow the vendor-supplied workaround (often a config flag or feature disable) and add detections for the published exploit pattern in your SIEM. Re-scan after the patch lands to confirm the finding clears.

    Where can I track exploitation activity?

    Watch CISA's Known Exploited Vulnerabilities catalog for CVE-2024-36913. Cross-reference with public exploit databases and your own SIEM/IDS for indicator-of-compromise patterns. Vulnios tracks KEV status automatically and surfaces it on the asset findings view.

    How does Vulnios help with this?

    Vulnios continuously cross-references your asset inventory against the live CVE feed (NVD, vendor advisories, CISA KEV, and curated OSINT). When a new CVE matches your environment, you get a prioritized finding with the severity, KEV status, exploit-prediction (EPSS), and a direct path to the vendor patch. You can start a free scan from the homepage.

    critical

    Protect Your Organization

    Monitor CVEs, scan for vulnerabilities, and get real-time threat alerts — all in one platform.

    Get Started FreeFree Security ScanOSINT Dashboard

    Weekly threat digest

    KEV-listed exploits and vendor advisories, every Monday.

    One email a week. Unsubscribe any time.

    Get instant alerts on Telegram

    Join our public channel for real-time critical CVE alerts.

    Follow @vulnios