CVE-2022-50717

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-12-24. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
55%
KEV
Not listed

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

nvmet-tcp: add bounds check on Transfer Tag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b6a545ffa2c192b1e6da4a7924edac5ba9f4ea2b
generic

nvmet-tcp: add bounds check on Transfer Tag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/752593d04637ebdc87fd29cba81897f21ae053f0
generic

nvmet-tcp: add bounds check on Transfer Tag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fcf82e4553db911d10234ff2390cfd0e2aa854e4
generic

nvmet-tcp: add bounds check on Transfer Tag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ec8adf767e1cfa7031f853b8c71ba1963f07df15
generic

nvmet-tcp: add bounds check on Transfer Tag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d5bb45f47b37d10f010355686b28c9ebacb361d4
generic

nvmet-tcp: add bounds check on Transfer Tag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d150ccd55dbfad36f55855b40b381884c98456e

Vendor Advisories for CVE-2022-50717(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-477.58.1.el8_82024-06-11redhat
redhatkernel-0:4.18.0-553.el8_102024-05-22redhat
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat
linuxKernel @ 5.4.220—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (22 versions)5.10.158-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—

Data Freshness Timeline

(refreshed 5× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 209 total refreshes for this CVE.

  1. 2026-09-16 14:05 UTCEPSS rescore
  2. 2026-09-16 05:11 UTCEPSS rescore
  3. 2026-09-15 03:07 UTCEPSS rescore
  4. 2026-09-14 05:50 UTCOSV refresh
  5. 2026-09-13 16:44 UTCEPSS rescore
  6. 2026-09-11 14:50 UTCEPSS rescore
  7. 2026-09-11 09:34 UTCEPSS rescore
  8. 2026-09-08 21:57 UTCEPSS rescore
  9. 2026-09-07 15:59 UTCEPSS rescore
  10. 2026-09-06 13:45 UTCEPSS rescore
  11. 2026-09-05 15:25 UTCEPSS rescore
  12. 2026-09-04 13:57 UTCEPSS rescore
  13. 2026-09-04 05:04 UTCEPSS rescore
  14. 2026-09-02 14:09 UTCEPSS rescore
  15. 2026-09-01 13:51 UTCEPSS rescore
  16. 2026-08-30 19:15 UTCEPSS rescore
  17. 2026-08-30 01:19 UTCEPSS rescore
  18. 2026-08-28 21:38 UTCEPSS rescore
  19. 2026-08-27 14:22 UTCEPSS rescore
  20. 2026-08-26 14:43 UTCEPSS rescore
  21. 2026-08-26 07:13 UTCOSV refresh
  22. 2026-08-25 13:46 UTCEPSS rescore
  23. 2026-08-23 00:17 UTCEPSS rescore
  24. 2026-08-21 23:46 UTCEPSS rescore
  25. 2026-08-20 22:53 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:01 UTCEPSS rescore
  2. 2026-08-18 13:45 UTCEPSS rescore
  3. 2026-08-17 13:44 UTCEPSS rescore
  4. 2026-08-16 14:53 UTCEPSS rescore
  5. 2026-08-16 02:12 UTCEPSS rescore
  6. 2026-08-15 01:27 UTCEPSS rescore
  7. 2026-08-13 21:58 UTCEPSS rescore
  8. 2026-08-12 13:48 UTCEPSS rescore
  9. 2026-08-09 22:52 UTCEG score recompute
  10. 2026-08-09 22:52 UTCVendor advisory
  11. 2026-08-09 22:52 UTCGHSA enrichment
  12. 2026-08-09 13:44 UTCEPSS rescore
  13. 2026-08-09 13:44 UTCEPSS rescore
  14. 2026-08-08 16:34 UTCEPSS rescore
  15. 2026-08-08 09:28 UTCVendor advisory
  16. 2026-08-08 09:28 UTCGHSA enrichment
  17. 2026-08-08 05:28 UTCEG score recompute
  18. 2026-08-08 05:28 UTCVendor advisory
  19. 2026-08-08 05:28 UTCGHSA enrichment
  20. 2026-08-07 16:24 UTCEPSS rescore
  21. 2026-08-06 13:44 UTCEPSS rescore
  22. 2026-08-06 07:15 UTCEG score recompute
  23. 2026-08-06 07:15 UTCVendor advisory
  24. 2026-08-06 07:15 UTCGHSA enrichment
  25. 2026-08-05 19:15 UTCEPSS rescore
  26. 2026-08-05 09:18 UTCEG score recompute
  27. 2026-08-05 09:18 UTCVendor advisory
  28. 2026-08-05 09:17 UTCGHSA enrichment
  29. 2026-08-04 15:07 UTCEPSS rescore
  30. 2026-08-04 10:51 UTCEG score recompute
  31. 2026-08-04 10:51 UTCVendor advisory
  32. 2026-08-04 10:51 UTCGHSA enrichment
  33. 2026-08-04 09:26 UTCEG score recompute▲ 9.80
  34. 2026-08-04 09:26 UTCVendor advisory
  35. 2026-08-04 09:25 UTCGHSA enrichment
  36. 2026-08-04 09:20 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  37. 2026-08-03 10:33 UTCEPSS rescore
  38. 2026-08-02 02:24 UTCEPSS rescore
  39. 2026-08-01 04:13 UTCEPSS rescore
  40. 2026-08-01 04:13 UTCEPSS rescore
  41. 2026-07-30 16:25 UTCEPSS rescore
  42. 2026-07-30 01:28 UTCEPSS rescore
  43. 2026-07-28 15:34 UTCEPSS rescore
  44. 2026-07-27 03:39 UTCOSV refresh
  45. 2026-07-26 14:52 UTCEPSS rescore
  46. 2026-07-26 14:52 UTCEPSS rescore
  47. 2026-07-25 14:16 UTCEPSS rescore
  48. 2026-07-24 14:15 UTCEPSS rescore
  49. 2026-07-23 14:16 UTCEPSS rescore
  50. 2026-07-23 14:16 UTCEPSS rescore
  51. 2026-07-23 02:17 UTCEG score recompute
  52. 2026-07-22 23:04 UTCEG score recompute
  53. 2026-07-22 14:06 UTCEPSS rescore
  54. 2026-07-22 14:06 UTCEPSS rescore
  55. 2026-07-21 15:23 UTCEPSS rescore
  56. 2026-07-21 15:23 UTCEPSS rescore
  57. 2026-07-20 17:05 UTCEPSS rescore
  58. 2026-07-19 14:29 UTCEPSS rescore
  59. 2026-07-19 14:29 UTCEPSS rescore
  60. 2026-07-19 02:27 UTCEPSS rescore
  61. 2026-07-19 02:27 UTCEPSS rescore
  62. 2026-07-18 10:03 UTCEPSS rescore
  63. 2026-07-18 10:03 UTCEPSS rescore
  64. 2026-07-16 17:00 UTCEPSS rescore
  65. 2026-07-15 16:56 UTCEPSS rescore
  66. 2026-07-15 16:56 UTCEPSS rescore
  67. 2026-07-15 01:58 UTCEPSS rescore
  68. 2026-07-15 01:58 UTCEPSS rescore
  69. 2026-07-13 22:28 UTCEPSS rescore
  70. 2026-07-13 22:28 UTCEPSS rescore
  71. 2026-07-13 06:11 UTCEPSS rescore
  72. 2026-07-13 06:11 UTCEPSS rescore
  73. 2026-07-12 05:44 UTCEPSS rescore
  74. 2026-07-11 08:25 UTCEPSS rescore
  75. 2026-07-11 08:25 UTCEPSS rescore

Frequently asked(5)

What is CVE-2022-50717?
CVE-2022-50717 is a critical vulnerability published on December 24, 2025. 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 nvmettcphandleh2cdata_pdu(), add a bounds check to avoid out-of-bounds access.
When was CVE-2022-50717 disclosed?
CVE-2022-50717 was first published in the National Vulnerability Database on December 24, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50717 actively exploited?
CVE-2022-50717 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 45.3% of all scored CVEs.
What is the CVSS score of CVE-2022-50717?
CVE-2022-50717 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-50717?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50717, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-50717

Explore →

Is Your Infrastructure Affected by CVE-2022-50717?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs