Back
CVE-2022-50717nvmet-tcp: add bounds check on Transfer Tag
- 9.8CriticalCVSS base score
- 0.82%Exploitation in 30 daysEPSS · top 42% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 7 months later
· 7 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.82% · top 42% of all CVEs (17 Nov 2026)
Loading the EPSS history…
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 0d150ccd55dbfad36f55855b40b381884c98456e
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < d5bb45f47b37d10f010355686b28c9ebacb361d4
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < ec8adf767e1cfa7031f853b8c71ba1963f07df15
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < fcf82e4553db911d10234ff2390cfd0e2aa854e4
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 752593d04637ebdc87fd29cba81897f21ae053f0
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < b6a545ffa2c192b1e6da4a7924edac5ba9f4ea2b
- affected 5.0
- unaffected < 5.0
- unaffected 5.4.220 – ≤ 5.4.*
- unaffected 5.10.150 – ≤ 5.10.*
- unaffected 5.15.75 – ≤ 5.15.*
- unaffected 5.19.17 – ≤ 5.19.*
- unaffected 6.0.3 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References
References6
- https://git.kernel.org/stable/c/0d150ccd55dbfad36f55855b40b381884c98456e (opens in a new tab)
- https://git.kernel.org/stable/c/d5bb45f47b37d10f010355686b28c9ebacb361d4 (opens in a new tab)
- https://git.kernel.org/stable/c/ec8adf767e1cfa7031f853b8c71ba1963f07df15 (opens in a new tab)
- https://git.kernel.org/stable/c/fcf82e4553db911d10234ff2390cfd0e2aa854e4 (opens in a new tab)
- https://git.kernel.org/stable/c/752593d04637ebdc87fd29cba81897f21ae053f0 (opens in a new tab)
- https://git.kernel.org/stable/c/b6a545ffa2c192b1e6da4a7924edac5ba9f4ea2b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-55772 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-50717)Record last updated .