{"schema_version":"1.9.0","id":"CVE-2022-49568","published":"2025-02-26T02:23:12.722Z","modified":"2026-08-12T03:51:43.220178092Z","related":["SUSE-SU-2025:1027-1","SUSE-SU-2025:1176-1","SUSE-SU-2025:1183-1","SUSE-SU-2025:1241-1"],"summary":"KVM: Don't null dereference ops->destroy","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: Don't null dereference ops->destroy\n\nA KVM device cleanup happens in either of two callbacks:\n1) destroy() which is called when the VM is being destroyed;\n2) release() which is called when a device fd is closed.\n\nMost KVM devices use 1) but Book3s's interrupt controller KVM devices\n(XICS, XIVE, XIVE-native) use 2) as they need to close and reopen during\nthe machine execution. The error handling in kvm_ioctl_create_device()\nassumes destroy() is always defined which leads to NULL dereference as\ndiscovered by Syzkaller.\n\nThis adds a checks for destroy!=NULL and adds a missing release().\n\nThis is not changing kvm_destroy_devices() as devices with defined\nrelease() should have been removed from the KVM devices list by then.","affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"852b6d57dc7fa378019786fa84727036e56839ea"},{"fixed":"170465715a60cbb7876e6b961b21bd3225469da8"},{"fixed":"3616776bc51cd3262bb1be60cc01c72e0a1959cf"},{"fixed":"e91665fbbf3ccb268b268a7d71a6513538d813ac"},{"fixed":"d4a5a79b780891c5cbdfdc6124d46fdf8d13dba1"},{"fixed":"e8bc2427018826e02add7b0ed0fc625a60390ae5"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49568.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.10.0"},{"fixed":"5.4.210"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.5.0"},{"fixed":"5.10.134"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.58"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"5.18.15"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49568.json"}}],"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/170465715a60cbb7876e6b961b21bd3225469da8"},{"type":"WEB","url":"https://git.kernel.org/stable/c/3616776bc51cd3262bb1be60cc01c72e0a1959cf"},{"type":"WEB","url":"https://git.kernel.org/stable/c/d4a5a79b780891c5cbdfdc6124d46fdf8d13dba1"},{"type":"WEB","url":"https://git.kernel.org/stable/c/e8bc2427018826e02add7b0ed0fc625a60390ae5"},{"type":"WEB","url":"https://git.kernel.org/stable/c/e91665fbbf3ccb268b268a7d71a6513538d813ac"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49568.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49568"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49568.json"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"}]}