CVE-2026-99216

Drivers: hv: Don't reset VMBus connection state on error/exit paths

  • High 8.4

Description

In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: Don't reset VMBus connection state on error/exit paths In two places, current code forces vmbus_connection.conn_state to DISCONNECTED prior to calling vmbus_disconnect(). But vmbus_disconnect() calls vmbus_initiate_unload(), which unloads the VMBus connection only if the conn_state is CONNECTED. Consequently, the connection remains and the Hyper-V host might continue to send messages or post VMBus interrupts. The problem was introduced in commit 74347a99e73ae ("x86/Hyper-V: Unload vmbus channel in hv panic callback"), in that vmbus_initiate_unload() started checking the current connection state before doing the unload. This commit removed some occurrences where conn_state was forced to DISCONNECTED, but these two remained, apparently due to an oversight at the time. Fix this by not forcing conn_state to DISCONNECTED during VMBus exit, or if a failure occurs when establishing the connection in the first place. Whatever value conn_state has at the time is then read by vmbus_initiate_unload() to determine if there is a connection to be unloaded.

Key facts

Published
28 Oct 2026
Last changed
31 Oct 2026
Assigned by
Linux
EPSS
0.137% likely to be exploited in the next 30 days, higher than 3.172% of CVEs (scores for 16 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.4CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 74347a99e73ae00b8385f1209aaea193c670f901 up to but excluding 2939215d57bc8e4189290544fca78f3809ac3ef8 (affected)
  • 74347a99e73ae00b8385f1209aaea193c670f901 up to but excluding a0ae955ba9a5067a157ebb8defb4a0a9cb1fc304 (affected)
  • 74347a99e73ae00b8385f1209aaea193c670f901 up to but excluding deef3ab5129ae4c45662c957cdab3739eb047fb1 (affected)
  • 74347a99e73ae00b8385f1209aaea193c670f901 up to but excluding 2e5ffbf1e41abbf6e02ce28115107938f55ff646 (affected)
  • 74347a99e73ae00b8385f1209aaea193c670f901 up to but excluding 2732210132f92aca0622b5134027990a809279d5 (affected)
  • 74347a99e73ae00b8385f1209aaea193c670f901 up to but excluding f47ce27af80b87cc684d5c12b65506af498ac7e5 (affected)
  • 74347a99e73ae00b8385f1209aaea193c670f901 up to but excluding 3195546a377c2d8d176d837e8baad5ce15d11195 (affected)
  • 74347a99e73ae00b8385f1209aaea193c670f901 up to but excluding ec31dc39e835ccde0930daccece8c492d28282fc (affected)
  • 5e059fc0f054309036d3f612bc8b0a502ca58545 (affected)
  • 9f38f7b46de0747c1909e8c557aa21715dce20c5 (affected)
  • caeeb3787167c884b955404a7e669fd77f267e44 (affected)
  • 4.19.118 up to but excluding 4.20 (affected)
  • 5.4.35 up to but excluding 5.5 (affected)
  • 5.6.7 up to but excluding 5.7 (affected)
LinuxLinux
  • Default status: affected
  • 5.7 (affected)
  • 0 up to but excluding 5.7 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.2.13 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 28 Oct 2026 Published

References