[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022605-CVE-2022-49566-66a0@gregkh>
Date: Wed, 26 Feb 2025 03:22:09 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49566: crypto: qat - fix memory leak in RSA
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
crypto: qat - fix memory leak in RSA
When an RSA key represented in form 2 (as defined in PKCS #1 V2.1) is
used, some components of the private key persist even after the TFM is
released.
Replace the explicit calls to free the buffers in qat_rsa_exit_tfm()
with a call to qat_rsa_clear_ctx() which frees all buffers referenced in
the TFM context.
The Linux kernel CVE team has assigned CVE-2022-49566 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.8 with commit 879f77e9071f029e1c9bd5a75814ecf51370f846 and fixed in 5.15.58 with commit a843925e0287eebb4aa808666bf22c664dfe4c53
Issue introduced in 4.8 with commit 879f77e9071f029e1c9bd5a75814ecf51370f846 and fixed in 5.18.15 with commit 0f967fdc09955221a1951a279481b0bf4d359941
Issue introduced in 4.8 with commit 879f77e9071f029e1c9bd5a75814ecf51370f846 and fixed in 5.19 with commit 80a52e1ee7757b742f96bfb0d58f0c14eb6583d0
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-49566
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/crypto/qat/qat_common/qat_asym_algs.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/a843925e0287eebb4aa808666bf22c664dfe4c53
https://git.kernel.org/stable/c/0f967fdc09955221a1951a279481b0bf4d359941
https://git.kernel.org/stable/c/80a52e1ee7757b742f96bfb0d58f0c14eb6583d0
Powered by blists - more mailing lists