[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091555-CVE-2022-50330-cd49@gregkh>
Date: Mon, 15 Sep 2025 16:49:07 +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-50330: crypto: cavium - prevent integer overflow loading firmware
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
crypto: cavium - prevent integer overflow loading firmware
The "code_length" value comes from the firmware file. If your firmware
is untrusted realistically there is probably very little you can do to
protect yourself. Still we try to limit the damage as much as possible.
Also Smatch marks any data read from the filesystem as untrusted and
prints warnings if it not capped correctly.
The "ntohl(ucode->code_length) * 2" multiplication can have an
integer overflow.
The Linux kernel CVE team has assigned CVE-2022-50330 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.11 with commit 9e2c7d99941d000a36f68a3594cec27a1bbea274 and fixed in 4.14.296 with commit c4d4c2afd08dfb3cd1c880d1811ede2568e81a6d
Issue introduced in 4.11 with commit 9e2c7d99941d000a36f68a3594cec27a1bbea274 and fixed in 4.19.262 with commit 90e483e7f20c32287d2a9da967e122938f52737a
Issue introduced in 4.11 with commit 9e2c7d99941d000a36f68a3594cec27a1bbea274 and fixed in 5.4.220 with commit 584561e94260268abe1c83e00d9c205565cb7bc5
Issue introduced in 4.11 with commit 9e2c7d99941d000a36f68a3594cec27a1bbea274 and fixed in 5.10.150 with commit 3a720eb89026c5241b8c4abb33370dc6fb565eee
Issue introduced in 4.11 with commit 9e2c7d99941d000a36f68a3594cec27a1bbea274 and fixed in 5.15.75 with commit 172c8a24fc8312cf6b88d3c88469653fdcb1c127
Issue introduced in 4.11 with commit 9e2c7d99941d000a36f68a3594cec27a1bbea274 and fixed in 5.19.17 with commit 371fa5129af53a79f6dddc90fe5bb0825cbe72a4
Issue introduced in 4.11 with commit 9e2c7d99941d000a36f68a3594cec27a1bbea274 and fixed in 6.0.3 with commit e29fd7a6852376d2cfb95ad5d6d3eeff93f815e9
Issue introduced in 4.11 with commit 9e2c7d99941d000a36f68a3594cec27a1bbea274 and fixed in 6.1 with commit 2526d6bf27d15054bb0778b2f7bc6625fd934905
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-50330
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/cavium/cpt/cptpf_main.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/c4d4c2afd08dfb3cd1c880d1811ede2568e81a6d
https://git.kernel.org/stable/c/90e483e7f20c32287d2a9da967e122938f52737a
https://git.kernel.org/stable/c/584561e94260268abe1c83e00d9c205565cb7bc5
https://git.kernel.org/stable/c/3a720eb89026c5241b8c4abb33370dc6fb565eee
https://git.kernel.org/stable/c/172c8a24fc8312cf6b88d3c88469653fdcb1c127
https://git.kernel.org/stable/c/371fa5129af53a79f6dddc90fe5bb0825cbe72a4
https://git.kernel.org/stable/c/e29fd7a6852376d2cfb95ad5d6d3eeff93f815e9
https://git.kernel.org/stable/c/2526d6bf27d15054bb0778b2f7bc6625fd934905
Powered by blists - more mailing lists