Medium · CVSS 5.5CVE-2022-50269

drm/vkms: Fix memory leak in vkms_init()CVE-2022-50269

Answer in brief

CVE-2022-50269 records a Medium severity (CVSS 5.5) vulnerability in drm/vkms: Fix memory leak in vkms_init(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 15, 2025Updated Nov 5, 2026Source checked Nov 5, 2026First seen by HOL Nov 5, 2026Material review Nov 5, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.5
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
Product	Affected versions	Fixed versions
cpe:2.3:o:linux:linux_kernel::::::::	Not reported	Not reported

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=2df7af93fdadb9ba8226fe443fae15ecdefda2a6 <bad13de764888b765ceaa4668893b52bd16653cc \|\| >=2df7af93fdadb9ba8226fe443fae15ecdefda2a6 <bebd60ec3bf21062f103e32e6203c6daabdbd51b \|\| >=2df7af93fdadb9ba8226fe443fae15ecdefda2a6 <07ab77154d6fd2d67e465ab5ce30083709950f02 \|\| >=2df7af93fdadb9ba8226fe443fae15ecdefda2a6 <0d0b368b9d104b437e1f4850ae94bdb9a3601e89	bad13de764888b765ceaa4668893b52bd16653cc, bebd60ec3bf21062f103e32e6203c6daabdbd51b, 07ab77154d6fd2d67e465ab5ce30083709950f02, 0d0b368b9d104b437e1f4850ae94bdb9a3601e89
Linux/Linuxgeneric	5.12	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to bad13de764888b765ceaa4668893b52bd16653cc if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 15, 2025
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Nov 5, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.