[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091504-CVE-2022-50269-24d9@gregkh>
Date: Mon, 15 Sep 2025 16:21:11 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50269: drm/vkms: Fix memory leak in vkms_init()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/vkms: Fix memory leak in vkms_init()
A memory leak was reported after the vkms module install failed.
unreferenced object 0xffff88810bc28520 (size 16):
comm "modprobe", pid 9662, jiffies 4298009455 (age 42.590s)
hex dump (first 16 bytes):
01 01 00 64 81 88 ff ff 00 00 dc 0a 81 88 ff ff ...d............
backtrace:
[<00000000e7561ff8>] kmalloc_trace+0x27/0x60
[<000000000b1954a0>] 0xffffffffc45200a9
[<00000000abbf1da0>] do_one_initcall+0xd0/0x4f0
[<000000001505ee87>] do_init_module+0x1a4/0x680
[<00000000958079ad>] load_module+0x6249/0x7110
[<00000000117e4696>] __do_sys_finit_module+0x140/0x200
[<00000000f74b12d2>] do_syscall_64+0x35/0x80
[<000000008fc6fcde>] entry_SYSCALL_64_after_hwframe+0x46/0xb0
The reason is that the vkms_init() returns without checking the return
value of vkms_create(), and if the vkms_create() failed, the config
allocated at the beginning of vkms_init() is leaked.
vkms_init()
config = kmalloc(...) # config allocated
...
return vkms_create() # vkms_create failed and config is leaked
Fix this problem by checking return value of vkms_create() and free the
config if error happened.
The Linux kernel CVE team has assigned CVE-2022-50269 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.12 with commit 2df7af93fdadb9ba8226fe443fae15ecdefda2a6 and fixed in 5.15.99 with commit bad13de764888b765ceaa4668893b52bd16653cc
Issue introduced in 5.12 with commit 2df7af93fdadb9ba8226fe443fae15ecdefda2a6 and fixed in 6.1.16 with commit bebd60ec3bf21062f103e32e6203c6daabdbd51b
Issue introduced in 5.12 with commit 2df7af93fdadb9ba8226fe443fae15ecdefda2a6 and fixed in 6.2.3 with commit 07ab77154d6fd2d67e465ab5ce30083709950f02
Issue introduced in 5.12 with commit 2df7af93fdadb9ba8226fe443fae15ecdefda2a6 and fixed in 6.3 with commit 0d0b368b9d104b437e1f4850ae94bdb9a3601e89
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-50269
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/vkms/vkms_drv.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/bad13de764888b765ceaa4668893b52bd16653cc
https://git.kernel.org/stable/c/bebd60ec3bf21062f103e32e6203c6daabdbd51b
https://git.kernel.org/stable/c/07ab77154d6fd2d67e465ab5ce30083709950f02
https://git.kernel.org/stable/c/0d0b368b9d104b437e1f4850ae94bdb9a3601e89
Powered by blists - more mailing lists