[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050124-CVE-2022-49795-e512@gregkh>
Date: Thu, 1 May 2025 16:09:45 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>,
"Masami Hiramatsu (Google)" <mhiramat@...nel.org>
Subject: CVE-2022-49795: rethook: fix a potential memleak in rethook_alloc()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
rethook: fix a potential memleak in rethook_alloc()
In rethook_alloc(), the variable rh is not freed or passed out
if handler is NULL, which could lead to a memleak, fix it.
[Masami: Add "rethook:" tag to the title.]
Acke-by: Masami Hiramatsu (Google) <mhiramat@...nel.org>
The Linux kernel CVE team has assigned CVE-2022-49795 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.18 with commit 54ecbe6f1ed5138c895bdff55608cf502755b20e and fixed in 6.0.10 with commit cbc5d1f9a8cc40ba2bc6779b36d2ea1f65bc027c
Issue introduced in 5.18 with commit 54ecbe6f1ed5138c895bdff55608cf502755b20e and fixed in 6.1 with commit 0a1ebe35cb3b7aa1f4b26b37e2a0b9ae68dc4ffb
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-49795
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/rethook.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/cbc5d1f9a8cc40ba2bc6779b36d2ea1f65bc027c
https://git.kernel.org/stable/c/0a1ebe35cb3b7aa1f4b26b37e2a0b9ae68dc4ffb
Powered by blists - more mailing lists