CVE-2026-99216

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.