Drivers: hv: Don't reset VMBus connection state on error/exit paths
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f47ce27af80b87cc684d5c12b65506af498ac7e5, Kernel 4.20, Kernel 5.5 and 15 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=74347a99e73ae00b8385f1209aaea193c670f901 <f47ce27af80b87cc684d5c12b65506af498ac7e5, >=4.19.118 <4.20, >=5.4.35 <5.5, >=5.6.7 <5.7, >=74347a99e73ae00b8385f1209aaea193c670f901 <2732210132f92aca0622b5134027990a809279d5, >=74347a99e73ae00b8385f1209aaea193c670f901 <2939215d57bc8e4189290544fca78f3809ac3ef8, >=74347a99e73ae00b8385f1209aaea193c670f901 <2e5ffbf1e41abbf6e02ce28115107938f55ff646, >=74347a99e73ae00b8385f1209aaea193c670f901 <3195546a377c2d8d176d837e8baad5ce15d11195, >=74347a99e73ae00b8385f1209aaea193c670f901 <a0ae955ba9a5067a157ebb8defb4a0a9cb1fc304, >=74347a99e73ae00b8385f1209aaea193c670f901 <deef3ab5129ae4c45662c957cdab3739eb047fb1, >=74347a99e73ae00b8385f1209aaea193c670f901 <ec31dc39e835ccde0930daccece8c492d28282fc, =5.7, =5e059fc0f054309036d3f612bc8b0a502ca58545, =9f38f7b46de0747c1909e8c557aa21715dce20c5, =caeeb3787167c884b955404a7e669fd77f267e44 | f47ce27af80b87cc684d5c12b65506af498ac7e5, 4.20, 5.5, 5.7, 2732210132f92aca0622b5134027990a809279d5, 2939215d57bc8e4189290544fca78f3809ac3ef8, 2e5ffbf1e41abbf6e02ce28115107938f55ff646, 3195546a377c2d8d176d837e8baad5ce15d11195, a0ae955ba9a5067a157ebb8defb4a0a9cb1fc304, deef3ab5129ae4c45662c957cdab3739eb047fb1, ec31dc39e835ccde0930daccece8c492d28282fc |
| linux-kernel: Kernel | >=5.11.0 <5.15.224, >=5.16.0 <6.1.191, >=5.4.35 <5.5, >=5.6.7 <5.7, >=5.7.0 <5.10.273, >=6.13.0 <6.18.59, >=6.19.0 <7.2.13, >=6.2.0 <6.6.161, >=6.7.0 <6.12.115, >=4.19.118 <4.20 | 5.15.224, 6.1.191, 5.5, 5.7, 5.10.273, 6.18.59, 7.2.13, 6.6.161, 6.12.115, 4.20 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket