CVE-2022-50269

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/vkms: Fix memory leak in vkms_init()<br /> <br /> A memory leak was reported after the vkms module install failed.<br /> <br /> unreferenced object 0xffff88810bc28520 (size 16):<br /> comm "modprobe", pid 9662, jiffies 4298009455 (age 42.590s)<br /> hex dump (first 16 bytes):<br /> 01 01 00 64 81 88 ff ff 00 00 dc 0a 81 88 ff ff ...d............<br /> backtrace:<br /> [] kmalloc_trace+0x27/0x60<br /> [] 0xffffffffc45200a9<br /> [] do_one_initcall+0xd0/0x4f0<br /> [] do_init_module+0x1a4/0x680<br /> [] load_module+0x6249/0x7110<br /> [] __do_sys_finit_module+0x140/0x200<br /> [] do_syscall_64+0x35/0x80<br /> [] entry_SYSCALL_64_after_hwframe+0x46/0xb0<br /> <br /> The reason is that the vkms_init() returns without checking the return<br /> value of vkms_create(), and if the vkms_create() failed, the config<br /> allocated at the beginning of vkms_init() is leaked.<br /> <br /> vkms_init()<br /> config = kmalloc(...) # config allocated<br /> ...<br /> return vkms_create() # vkms_create failed and config is leaked<br /> <br /> Fix this problem by checking return value of vkms_create() and free the<br /> config if error happened.