[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122416-CVE-2022-50717-dc68@gregkh>
Date: Wed, 24 Dec 2025 13:26:16 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50717: nvmet-tcp: add bounds check on Transfer Tag
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nvmet-tcp: add bounds check on Transfer Tag
ttag is used as an index to get cmd in nvmet_tcp_handle_h2c_data_pdu(),
add a bounds check to avoid out-of-bounds access.
The Linux kernel CVE team has assigned CVE-2022-50717 to this issue.
Affected and fixed versions
===========================
Fixed in 5.4.220 with commit 0d150ccd55dbfad36f55855b40b381884c98456e
Fixed in 5.10.150 with commit d5bb45f47b37d10f010355686b28c9ebacb361d4
Fixed in 5.15.75 with commit ec8adf767e1cfa7031f853b8c71ba1963f07df15
Fixed in 5.19.17 with commit fcf82e4553db911d10234ff2390cfd0e2aa854e4
Fixed in 6.0.3 with commit 752593d04637ebdc87fd29cba81897f21ae053f0
Fixed in 6.1 with commit b6a545ffa2c192b1e6da4a7924edac5ba9f4ea2b
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-50717
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/nvme/target/tcp.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/0d150ccd55dbfad36f55855b40b381884c98456e
https://git.kernel.org/stable/c/d5bb45f47b37d10f010355686b28c9ebacb361d4
https://git.kernel.org/stable/c/ec8adf767e1cfa7031f853b8c71ba1963f07df15
https://git.kernel.org/stable/c/fcf82e4553db911d10234ff2390cfd0e2aa854e4
https://git.kernel.org/stable/c/752593d04637ebdc87fd29cba81897f21ae053f0
https://git.kernel.org/stable/c/b6a545ffa2c192b1e6da4a7924edac5ba9f4ea2b
Powered by blists - more mailing lists