{"id":"CVE-2022-50369","summary":"drm/vkms: Fix null-ptr-deref in vkms_release()","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vkms: Fix null-ptr-deref in vkms_release()\n\nA null-ptr-deref is triggered when it tries to destroy the workqueue in\nvkms-\u003eoutput.composer_workq in vkms_release().\n\n KASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\n CPU: 5 PID: 17193 Comm: modprobe Not tainted 6.0.0-11331-gd465bff130bf #24\n RIP: 0010:destroy_workqueue+0x2f/0x710\n ...\n Call Trace:\n  \u003cTASK\u003e\n  ? vkms_config_debugfs_init+0x50/0x50 [vkms]\n  __devm_drm_dev_alloc+0x15a/0x1c0 [drm]\n  vkms_init+0x245/0x1000 [vkms]\n  do_one_initcall+0xd0/0x4f0\n  do_init_module+0x1a4/0x680\n  load_module+0x6249/0x7110\n  __do_sys_finit_module+0x140/0x200\n  do_syscall_64+0x35/0x80\n  entry_SYSCALL_64_after_hwframe+0x46/0xb0\n\nThe reason is that an OOM happened which triggers the destroy of the\nworkqueue, however, the workqueue is alloced in the later process,\nthus a null-ptr-deref happened. A simple call graph is shown as below:\n\n vkms_init()\n  vkms_create()\n    devm_drm_dev_alloc()\n      __devm_drm_dev_alloc()\n        devm_drm_dev_init()\n          devm_add_action_or_reset()\n            devm_add_action() # an error happened\n            devm_drm_dev_init_release()\n              drm_dev_put()\n                kref_put()\n                  drm_dev_release()\n                    vkms_release()\n                      destroy_workqueue() # null-ptr-deref happened\n    vkms_modeset_init()\n      vkms_output_init()\n        vkms_crtc_init() # where the workqueue get allocated\n\nFix this by checking if composer_workq is NULL before passing it to\nthe destroy_workqueue() in vkms_release().","modified":"2026-04-02T08:28:26.994983Z","published":"2025-09-17T14:56:24.889Z","related":["SUSE-SU-2025:03615-1","SUSE-SU-2025:03628-1","SUSE-SU-2025:3716-1","SUSE-SU-2025:3761-1"],"database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50369.json","cna_assigner":"Linux"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/0b8f390e2251191f1b179cc87f65d54c96565f0d"},{"type":"WEB","url":"https://git.kernel.org/stable/c/1f9836f95271e7acf016667eee0aeae3386f9645"},{"type":"WEB","url":"https://git.kernel.org/stable/c/2fe2a8f40c21161ffe7653cc234e7934db5b7cc5"},{"type":"WEB","url":"https://git.kernel.org/stable/c/57031c474c3a920ea73afeb5dc352e537f5793ee"},{"type":"WEB","url":"https://git.kernel.org/stable/c/596f1ba3987e601e31a5abf1f75ce1d2635aceac"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50369.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50369"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"6c234fe37c57627a5baf96f552afa1fae2b67d4d"},{"fixed":"0b8f390e2251191f1b179cc87f65d54c96565f0d"},{"fixed":"1f9836f95271e7acf016667eee0aeae3386f9645"},{"fixed":"596f1ba3987e601e31a5abf1f75ce1d2635aceac"},{"fixed":"57031c474c3a920ea73afeb5dc352e537f5793ee"},{"fixed":"2fe2a8f40c21161ffe7653cc234e7934db5b7cc5"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50369.json"}}],"schema_version":"1.7.5","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"}]}