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.
- Status
- Received - 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- Published
- 2026-10-28
- Last modified
- 2026-10-28
Affected products
References
- https://git.kernel.org/stable/c/f47ce27af80b87cc684d5c12b65506af498ac7e5
- https://git.kernel.org/stable/c/3195546a377c2d8d176d837e8baad5ce15d11195
- https://git.kernel.org/stable/c/ec31dc39e835ccde0930daccece8c492d28282fc
