CVE-2022-50269drm/vkms: Fix memory leak in vkms_init()
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 14 months later
· 14 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 2df7af93fdadb9ba8226fe443fae15ecdefda2a6 – < bad13de764888b765ceaa4668893b52bd16653cc
- affected 2df7af93fdadb9ba8226fe443fae15ecdefda2a6 – < bebd60ec3bf21062f103e32e6203c6daabdbd51b
- affected 2df7af93fdadb9ba8226fe443fae15ecdefda2a6 – < 07ab77154d6fd2d67e465ab5ce30083709950f02
- affected 2df7af93fdadb9ba8226fe443fae15ecdefda2a6 – < 0d0b368b9d104b437e1f4850ae94bdb9a3601e89
- affected 5.12
- unaffected < 5.12
- unaffected 5.15.99 – ≤ 5.15.*
- unaffected 6.1.16 – ≤ 6.1.*
- unaffected 6.2.3 – ≤ 6.2.*
- unaffected 6.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/bad13de764888b765ceaa4668893b52bd16653cc (opens in a new tab)
- https://git.kernel.org/stable/c/bebd60ec3bf21062f103e32e6203c6daabdbd51b (opens in a new tab)
- https://git.kernel.org/stable/c/07ab77154d6fd2d67e465ab5ce30083709950f02 (opens in a new tab)
- https://git.kernel.org/stable/c/0d0b368b9d104b437e1f4850ae94bdb9a3601e89 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-55586 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-50269)Record last updated .