linux-cve-announce - CVE-2022-50075: tracing/eprobes: Have event probes be consistent with kprobes and uprobes

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: <2025061854-CVE-2022-50075-f791@gregkh>
Date: Wed, 18 Jun 2025 13:02:20 +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-50075: tracing/eprobes: Have event probes be consistent with kprobes and uprobes

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

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

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

tracing/eprobes: Have event probes be consistent with kprobes and uprobes

Currently, if a symbol "@" is attempted to be used with an event probe
(eprobes), it will cause a NULL pointer dereference crash.

Both kprobes and uprobes can reference data other than the main registers.
Such as immediate address, symbols and the current task name. Have eprobes
do the same thing.

For "comm", if "comm" is used and the event being attached to does not
have the "comm" field, then make it the "$comm" that kprobes has. This is
consistent to the way histograms and filters work.

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


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

	Issue introduced in 5.15 with commit 7491e2c442781a1860181adb5ab472a52075f393 and fixed in 5.15.63 with commit b489aca082a23033a3d8355cfb0032f0e2523440
	Issue introduced in 5.15 with commit 7491e2c442781a1860181adb5ab472a52075f393 and fixed in 5.19.4 with commit 47cc883f21fa3bcf24891b4b455f4cd461ce2d6e
	Issue introduced in 5.15 with commit 7491e2c442781a1860181adb5ab472a52075f393 and fixed in 6.0 with commit 6a832ec3d680b3a4f4fad5752672827d71bae501

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-50075
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:
	kernel/trace/trace_eprobe.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/b489aca082a23033a3d8355cfb0032f0e2523440
	https://git.kernel.org/stable/c/47cc883f21fa3bcf24891b4b455f4cd461ce2d6e
	https://git.kernel.org/stable/c/6a832ec3d680b3a4f4fad5752672827d71bae501