KVM: Don't null dereference ops->destroy
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 170465715a60cbb7876e6b961b21bd3225469da8, Kernel 3616776bc51cd3262bb1be60cc01c72e0a1959cf, Kernel d4a5a79b780891c5cbdfdc6124d46fdf8d13dba1 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: KVM: Don't null dereference ops->destroy A KVM device cleanup happens in either of two callbacks: 1) destroy() which is called when the VM is being destroyed; 2) release() which is called when a device fd is closed. Most KVM devices use 1) but Book3s's interrupt controller KVM devices (XICS, XIVE, XIVE-native) use 2) as they need to close and reopen during the machine execution. The error handling in kvm_ioctl_create_device() assumes destroy() is always defined which leads to NULL dereference as discovered by Syzkaller. This adds a checks for destroy!=NULL and adds a missing release(). This is not changing kvm_destroy_devices() as devices with defined release() should have been removed from the KVM devices list by then.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.10, >=852b6d57dc7fa378019786fa84727036e56839ea <170465715a60cbb7876e6b961b21bd3225469da8, >=852b6d57dc7fa378019786fa84727036e56839ea <3616776bc51cd3262bb1be60cc01c72e0a1959cf, >=852b6d57dc7fa378019786fa84727036e56839ea <d4a5a79b780891c5cbdfdc6124d46fdf8d13dba1, >=852b6d57dc7fa378019786fa84727036e56839ea <e8bc2427018826e02add7b0ed0fc625a60390ae5, >=852b6d57dc7fa378019786fa84727036e56839ea <e91665fbbf3ccb268b268a7d71a6513538d813ac | 170465715a60cbb7876e6b961b21bd3225469da8, 3616776bc51cd3262bb1be60cc01c72e0a1959cf, d4a5a79b780891c5cbdfdc6124d46fdf8d13dba1, e8bc2427018826e02add7b0ed0fc625a60390ae5, e91665fbbf3ccb268b268a7d71a6513538d813ac |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket