linux-cve-announce - CVE-2022-50080: tee: add overflow check in register_shm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025061856-CVE-2022-50080-a32c@gregkh>
Date: Wed, 18 Jun 2025 13:02:25 +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-50080: tee: add overflow check in register_shm_helper()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

tee: add overflow check in register_shm_helper()

With special lengths supplied by user space, register_shm_helper() has
an integer overflow when calculating the number of pages covered by a
supplied user space memory region.

This causes internal_get_user_pages_fast() a helper function of
pin_user_pages_fast() to do a NULL pointer dereference:

  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010
  Modules linked in:
  CPU: 1 PID: 173 Comm: optee_example_a Not tainted 5.19.0 #11
  Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015
  pc : internal_get_user_pages_fast+0x474/0xa80
  Call trace:
   internal_get_user_pages_fast+0x474/0xa80
   pin_user_pages_fast+0x24/0x4c
   register_shm_helper+0x194/0x330
   tee_shm_register_user_buf+0x78/0x120
   tee_ioctl+0xd0/0x11a0
   __arm64_sys_ioctl+0xa8/0xec
   invoke_syscall+0x48/0x114

Fix this by adding an an explicit call to access_ok() in
tee_shm_register_user_buf() to catch an invalid user space address
early.

The Linux kernel CVE team has assigned CVE-2022-50080 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.16 with commit 033ddf12bcf5326b93bd604f50a7474a434a35f9 and fixed in 4.19.256 with commit b37e0f17653c00b586cdbcdf0dbca475358ecffd
	Issue introduced in 4.16 with commit 033ddf12bcf5326b93bd604f50a7474a434a35f9 and fixed in 5.4.211 with commit 965333345fe952cc7eebc8e3a565ffc709441af2
	Issue introduced in 4.16 with commit 033ddf12bcf5326b93bd604f50a7474a434a35f9 and fixed in 5.10.137 with commit 578c349570d2a912401963783b36e0ec7a25c053
	Issue introduced in 4.16 with commit 033ddf12bcf5326b93bd604f50a7474a434a35f9 and fixed in 5.15.62 with commit c12f0e6126ad223806a365084e86370511654bf1
	Issue introduced in 4.16 with commit 033ddf12bcf5326b93bd604f50a7474a434a35f9 and fixed in 5.18.19 with commit 2f8e79a1a6128214cb9b205a9869341af5dfb16b
	Issue introduced in 4.16 with commit 033ddf12bcf5326b93bd604f50a7474a434a35f9 and fixed in 5.19.3 with commit 58c008d4d398f792ca67f35650610864725518fd
	Issue introduced in 4.16 with commit 033ddf12bcf5326b93bd604f50a7474a434a35f9 and fixed in 6.0 with commit 573ae4f13f630d6660008f1974c0a8a29c30e18a

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-50080
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/tee/tee_shm.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/b37e0f17653c00b586cdbcdf0dbca475358ecffd
	https://git.kernel.org/stable/c/965333345fe952cc7eebc8e3a565ffc709441af2
	https://git.kernel.org/stable/c/578c349570d2a912401963783b36e0ec7a25c053
	https://git.kernel.org/stable/c/c12f0e6126ad223806a365084e86370511654bf1
	https://git.kernel.org/stable/c/2f8e79a1a6128214cb9b205a9869341af5dfb16b
	https://git.kernel.org/stable/c/58c008d4d398f792ca67f35650610864725518fd
	https://git.kernel.org/stable/c/573ae4f13f630d6660008f1974c0a8a29c30e18a