Skip to content

SystemsCritical 9.3Patch available

CVE-2026-99544

Hyper-V VMBus bounds bug lets host cause guest kernel memory writes.

How scary is it?

updated 22 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • No

    Reachable over the network1

    Needs local access to the machine, such as a shell or a logged-in user (CVSS AV:L).

  • None known

    Public exploit code is out

    None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

  • None known

    Attacks seen in the wild

    None reported that we know of.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run Linux in an affected version>= 3e7ee4902fe6996048f03433dd111426db3cfa92 and < cdb9126a79b608b4331dfdc03beb05be8d2563be / >= 3e7ee4902fe6996048f03433dd111426db3cfa92 and < f204bb7c5d10482067e095af567c391bc88ecb44 / >= 3e7ee4902fe6996048f03433dd111426db3cfa92 and < 1611ce4dc6cbace75f27db6a559af8d391a06118 (+2 more)

    >= 3e7ee4902fe6996048f03433dd111426db3cfa92 and < cdb9126a79b608b4331dfdc03beb05be8d2563be >= 3e7ee4902fe6996048f03433dd111426db3cfa92 and < f204bb7c5d10482067e095af567c391bc88ecb44 >= 3e7ee4902fe6996048f03433dd111426db3cfa92 and < 1611ce4dc6cbace75f27db6a559af8d391a06118 >= 3e7ee4902fe6996048f03433dd111426db3cfa92 and < 1d287c17cc5bfd6386fe0770999be410b248d021 2.6.32

    Vendor says fixed in: < 2.6.32, >= 6.12.117 and <= 6.12.*, >= 6.18.61 and <= 6.18.*, >= 7.3.2 and <= 7.3.*, >= 7.4-rc1 and <= *.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. The attacker already has local access to the machine

    CVSS attack vector: Local (AV:L). Local access required, such as a shell or a logged-in user.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per the vendorUpgrade to a fixed release< 2.6.32 / >= 6.12.117 and <= 6.12.* / >= 6.18.61 and <= 6.18.* / >= 7.3.2 and <= 7.3.* (+1 more)

    Linux: < 2.6.32, >= 6.12.117 and <= 6.12.*, >= 6.18.61 and <= 6.18.*, >= 7.3.2 and <= 7.3.*, >= 7.4-rc1 and <= *

    Fixed releases as stated by the vendor in the CVE record.

    See the affected products table · Source 1

  2. Recommendation, AI-writtenApply vendor/kernel update with hv:vmbus bounds-check patch and reboot affected guests.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

CVSS
9.3Criticalscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
No score yet
Fix
Fixed in < 2.6.32, >= 6.12.117 and <= 6.12.*, >= 6.18.61 and <= 6.18.*per the vendor; 2 more listed below
Published
19 Nov 2026analysed here 22 Nov 2026

Do first. Upgrade to a fixed release: < 2.6.32, >= 6.12.117 and <= 6.12.*, >= 6.18.61 and <= 6.18.*, >= 7.3.2 and <= 7.3.* (and 1 more below).

Summary

Impact

Untrusted host can force guest to write beyond ring buffer, causing kernel memory corruption, crashes, or arbitrary code execution in the guest VM.

Triage

Exploitable
At runtime
Attack vector
local
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Linux>= 3e7ee4902fe6996048f03433dd111426db3cfa92 and < cdb9126a79b608b4331dfdc03beb05be8d2563be>= 3e7ee4902fe6996048f03433dd111426db3cfa92 and < f204bb7c5d10482067e095af567c391bc88ecb44>= 3e7ee4902fe6996048f03433dd111426db3cfa92 and < 1611ce4dc6cbace75f27db6a559af8d391a06118>= 3e7ee4902fe6996048f03433dd111426db3cfa92 and < 1d287c17cc5bfd6386fe0770999be410b248d0212.6.32Vendor says fixed in: < 2.6.32, >= 6.12.117 and <= 6.12.*, >= 6.18.61 and <= 6.18.*, >= 7.3.2 and <= 7.3.*, >= 7.4-rc1 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Linux kernel (hv:vmbus driver)
  • Linux guests on Microsoft Hyper-V / CoCo VMs

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

Timeline

  1. 19 Nov 2026Published
  2. 22 Nov 2026CVE record last updated3 days later
  3. 22 Nov 2026Analysed by vulneraibility.comsame day later

Common questions

Is CVE-2026-99544 being exploited?

Not confirmed. CVE-2026-99544 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-99544?

CVE-2026-99544 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-99544?

Yes. A fix has been recorded for CVE-2026-99544. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-99544 affect?

CVE-2026-99544 affects Linux kernel (hv:vmbus driver), Linux guests on Microsoft Hyper-V / CoCo VMs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-99544?

Apply vendor/kernel update with hv:vmbus bounds-check patch and reboot affected guests.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

4 references in the CVE record, grouped by the tags the record gives them.

Other links (4)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.