linux-cve-announce - CVE-2022-49798: tracing: Fix race where eprobes can be called before the event

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 for Android: free password hash cracker in your pocket

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

Message-ID: <2025050125-CVE-2022-49798-7e07@gregkh>
Date: Thu,  1 May 2025 16:09:48 +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-49798: tracing: Fix race where eprobes can be called before the event

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

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

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

tracing: Fix race where eprobes can be called before the event

The flag that tells the event to call its triggers after reading the event
is set for eprobes after the eprobe is enabled. This leads to a race where
the eprobe may be triggered at the beginning of the event where the record
information is NULL. The eprobe then dereferences the NULL record causing
a NULL kernel pointer bug.

Test for a NULL record to keep this from happening.

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


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

	Issue introduced in 5.15 with commit 7491e2c442781a1860181adb5ab472a52075f393 and fixed in 5.15.80 with commit 7291dec4f2d17a2d3fd1f789fb41e58476539f21
	Issue introduced in 5.15 with commit 7491e2c442781a1860181adb5ab472a52075f393 and fixed in 6.0.10 with commit 73f5191467ffe3af82f27fe0ea6a8c2fac724d3f
	Issue introduced in 5.15 with commit 7491e2c442781a1860181adb5ab472a52075f393 and fixed in 6.1 with commit 94eedf3dded5fb472ce97bfaf3ac1c6c29c35d26

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-49798
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/7291dec4f2d17a2d3fd1f789fb41e58476539f21
	https://git.kernel.org/stable/c/73f5191467ffe3af82f27fe0ea6a8c2fac724d3f
	https://git.kernel.org/stable/c/94eedf3dded5fb472ce97bfaf3ac1c6c29c35d26