Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel cee0d90bceae1dee3bcc70f8d6b2ceb5b87deb42, Kernel 321f650493d6b8169dacd4d5d6f63550dce54d6c, Kernel 4c19c302cc577bd6b466f6d8e97971777392c2fa and 8 more.
In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition The VMBus module initialization function, hv_acpi_init(), currently does nothing when running in the root partition and root is not nested in another VM. But the initialization function reports success, so the VMBus module is indeed loaded. VMBus functionality is not actually needed, but the VMBus module must be loaded so that hv_vmbus_exists() can answer correctly. Furthermore, the mshv_root dependency on the VMBus module is needed as described in the commit message for 840b740a35bf ("mshv: Add conditional VMBus dependency"). Loading the VMBus module without actually initializing it causes failures if the module should later be unloaded. The module unload code tries to clean up things that were never initialized, resulting in memory faults and a panic. Fix this by having VMBus module exit function perform the same check for non-nested root partition, and do nothing in such a case, just like hv_acpi_init(). In the long run, the code that manages the Hyper-V provided SynIC should be refactored to better coordinate the requirements of root partition scenarios and normal VM scenarios, and to hopefully remove the hv_vmbus_exists() dependnecy between mshv_root and VMBus modules. Preventing the current unload failure scenario is an expediency until such a refactoring is done.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=7e279d78664aa91107ebff4b03eca367967f5908 <cee0d90bceae1dee3bcc70f8d6b2ceb5b87deb42, >=7e279d78664aa91107ebff4b03eca367967f5908 <321f650493d6b8169dacd4d5d6f63550dce54d6c, >=7e279d78664aa91107ebff4b03eca367967f5908 <4c19c302cc577bd6b466f6d8e97971777392c2fa, >=7e279d78664aa91107ebff4b03eca367967f5908 <4cc1ba2b31065a48fde14e9d53ad399a3ca32e35, >=7e279d78664aa91107ebff4b03eca367967f5908 <aa17842bbccaeaba7d05c166019d1c96a41bca54, >=7e279d78664aa91107ebff4b03eca367967f5908 <ca1f4a926d08035c52c735a42200e4e5ea548f32, =5.12 | cee0d90bceae1dee3bcc70f8d6b2ceb5b87deb42, 321f650493d6b8169dacd4d5d6f63550dce54d6c, 4c19c302cc577bd6b466f6d8e97971777392c2fa, 4cc1ba2b31065a48fde14e9d53ad399a3ca32e35, aa17842bbccaeaba7d05c166019d1c96a41bca54, ca1f4a926d08035c52c735a42200e4e5ea548f32 |
| linux-kernel: Kernel | >=6.13.0 <6.18.52, >=6.19.0 <7.2.6, >=6.2.0 <6.6.160, >=6.7.0 <6.12.114, >=5.12.0 <6.1.191 | 6.18.52, 7.2.6, 6.6.160, 6.12.114, 6.1.191 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket