linux-cve-announce - CVE-2022-50142: intel_th: msu: Fix vmalloced buffers

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: <2025061819-CVE-2022-50142-c569@gregkh>
Date: Wed, 18 Jun 2025 13:03:27 +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-50142: intel_th: msu: Fix vmalloced buffers

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

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

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

intel_th: msu: Fix vmalloced buffers

After commit f5ff79fddf0e ("dma-mapping: remove CONFIG_DMA_REMAP") there's
a chance of DMA buffer getting allocated via vmalloc(), which messes up
the mmapping code:

> RIP: msc_mmap_fault [intel_th_msu]
> Call Trace:
>  <TASK>
>  __do_fault
>  do_fault
...

Fix this by accounting for vmalloc possibility.

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


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

	Issue introduced in 5.2 with commit ba39bd8306057fb343dfb75d93a76d824b625236 and fixed in 5.4.211 with commit b5d924cb4c7b952eaa61622f14427723a78137a3
	Issue introduced in 5.2 with commit ba39bd8306057fb343dfb75d93a76d824b625236 and fixed in 5.10.137 with commit 6ae2881c1d1fa0e33f4763b7c786f8ef05a9c828
	Issue introduced in 5.2 with commit ba39bd8306057fb343dfb75d93a76d824b625236 and fixed in 5.15.61 with commit 566887bad7ff2297d6b3f9659c702ba075f3d62d
	Issue introduced in 5.2 with commit ba39bd8306057fb343dfb75d93a76d824b625236 and fixed in 5.18.18 with commit 0ed72c6bc632cbf8d979ac60f982ff84b7bb610a
	Issue introduced in 5.2 with commit ba39bd8306057fb343dfb75d93a76d824b625236 and fixed in 5.19.2 with commit 4914c50670b6a531e2cb17cd984cc565b4681312
	Issue introduced in 5.2 with commit ba39bd8306057fb343dfb75d93a76d824b625236 and fixed in 6.0 with commit ac12ad3ccf6d386e64a9d6a890595a2509d24edd

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-50142
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/hwtracing/intel_th/msu.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/b5d924cb4c7b952eaa61622f14427723a78137a3
	https://git.kernel.org/stable/c/6ae2881c1d1fa0e33f4763b7c786f8ef05a9c828
	https://git.kernel.org/stable/c/566887bad7ff2297d6b3f9659c702ba075f3d62d
	https://git.kernel.org/stable/c/0ed72c6bc632cbf8d979ac60f982ff84b7bb610a
	https://git.kernel.org/stable/c/4914c50670b6a531e2cb17cd984cc565b4681312
	https://git.kernel.org/stable/c/ac12ad3ccf6d386e64a9d6a890595a2509d24edd