[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025100754-CVE-2022-50538-3f3d@gregkh>
Date: Tue, 7 Oct 2025 17:20:56 +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-50538: vme: Fix error not catched in fake_init()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
vme: Fix error not catched in fake_init()
In fake_init(), __root_device_register() is possible to fail but it's
ignored, which can cause unregistering vme_root fail when exit.
general protection fault,
probably for non-canonical address 0xdffffc000000008c
KASAN: null-ptr-deref in range [0x0000000000000460-0x0000000000000467]
RIP: 0010:root_device_unregister+0x26/0x60
Call Trace:
<TASK>
__x64_sys_delete_module+0x34f/0x540
do_syscall_64+0x38/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Return error when __root_device_register() fails.
The Linux kernel CVE team has assigned CVE-2022-50538 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.9 with commit 658bcdae9c6755806e66b33e29d56b33a3ff421a and fixed in 4.9.337 with commit e831fdd60e5863ee03173baf5a0f7c5450b44381
Issue introduced in 4.9 with commit 658bcdae9c6755806e66b33e29d56b33a3ff421a and fixed in 4.14.303 with commit 69b43937f14bdc3594f57f1a507a14f3d1187136
Issue introduced in 4.9 with commit 658bcdae9c6755806e66b33e29d56b33a3ff421a and fixed in 4.19.270 with commit 09be0e7ac5f9374b6f8de72c89ed67129af71f65
Issue introduced in 4.9 with commit 658bcdae9c6755806e66b33e29d56b33a3ff421a and fixed in 5.4.229 with commit f3f65c4177846c483bf009f8c512ab04b3c62466
Issue introduced in 4.9 with commit 658bcdae9c6755806e66b33e29d56b33a3ff421a and fixed in 5.10.163 with commit 37d3de40c1ffb6a5e626bf46ff5ef5766c824e2c
Issue introduced in 4.9 with commit 658bcdae9c6755806e66b33e29d56b33a3ff421a and fixed in 5.15.86 with commit 4bc217b25ea81034fad8e33fd33e4659f086421d
Issue introduced in 4.9 with commit 658bcdae9c6755806e66b33e29d56b33a3ff421a and fixed in 6.0.16 with commit a2a93546d414c7fe4862b87183fb737d1300d9d2
Issue introduced in 4.9 with commit 658bcdae9c6755806e66b33e29d56b33a3ff421a and fixed in 6.1.2 with commit 60ff9bd4ffc87bace581e235a6728f5ac8e5071f
Issue introduced in 4.9 with commit 658bcdae9c6755806e66b33e29d56b33a3ff421a and fixed in 6.2 with commit 7bef797d707f1744f71156b21d41e3b8c946631f
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-50538
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/staging/vme_user/vme_fake.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/e831fdd60e5863ee03173baf5a0f7c5450b44381
https://git.kernel.org/stable/c/69b43937f14bdc3594f57f1a507a14f3d1187136
https://git.kernel.org/stable/c/09be0e7ac5f9374b6f8de72c89ed67129af71f65
https://git.kernel.org/stable/c/f3f65c4177846c483bf009f8c512ab04b3c62466
https://git.kernel.org/stable/c/37d3de40c1ffb6a5e626bf46ff5ef5766c824e2c
https://git.kernel.org/stable/c/4bc217b25ea81034fad8e33fd33e4659f086421d
https://git.kernel.org/stable/c/a2a93546d414c7fe4862b87183fb737d1300d9d2
https://git.kernel.org/stable/c/60ff9bd4ffc87bace581e235a6728f5ac8e5071f
https://git.kernel.org/stable/c/7bef797d707f1744f71156b21d41e3b8c946631f
Powered by blists - more mailing lists