[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050146-CVE-2022-49858-a1ee@gregkh>
Date: Thu, 1 May 2025 16:10: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-49858: octeontx2-pf: Fix SQE threshold checking
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
octeontx2-pf: Fix SQE threshold checking
Current way of checking available SQE count which is based on
HW updated SQB count could result in driver submitting an SQE
even before CQE for the previously transmitted SQE at the same
index is processed in NAPI resulting losing SKB pointers,
hence a leak. Fix this by checking a consumer index which
is updated once CQE is processed.
The Linux kernel CVE team has assigned CVE-2022-49858 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.6 with commit 3ca6c4c882a7f34085b170d93cf0d0e843aa00e6 and fixed in 6.0.9 with commit 015e3c0a3b16193aab23beefe4719484b9984c2d
Issue introduced in 5.6 with commit 3ca6c4c882a7f34085b170d93cf0d0e843aa00e6 and fixed in 6.1 with commit f0dfc4c88ef39be0ba736aa0ce6119263fc19aeb
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-49858
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/net/ethernet/marvell/octeontx2/nic/otx2_common.c
drivers/net/ethernet/marvell/octeontx2/nic/otx2_txrx.c
drivers/net/ethernet/marvell/octeontx2/nic/otx2_txrx.h
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/015e3c0a3b16193aab23beefe4719484b9984c2d
https://git.kernel.org/stable/c/f0dfc4c88ef39be0ba736aa0ce6119263fc19aeb
Powered by blists - more mailing lists