CVE-2022-50614

UNRATEDCVSS · not yet scored

Also known asEUVD-2022-55698 (ENISA EUVD) · GHSA-3xmp-jf8j-rjxp (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic

The dma_map_single() doesn't permit zero length mapping. It causes a follow panic.

A panic was reported on arm64:

[ 60.137988] ------------[ cut here ]------------ [ 60.142630] kernel BUG at kernel/dma/swiotlb.c:624! [ 60.147508] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP [ 60.152992] Modules linked in: dw_hdmi_cec crct10dif_ce simple_bridge rcar_fdp1 vsp1 rcar_vin videobuf2_vmalloc rcar_csi2 v4l 2_mem2mem videobuf2_dma_contig videobuf2_memops pci_endpoint_test videobuf2_v4l2 videobuf2_common rcar_fcp v4l2_fwnode v4l2_asyn c videodev mc gpio_bd9571mwv max9611 pwm_rcar ccree at24 authenc libdes phy_rcar_gen3_usb3 usb_dmac display_connector pwm_bl [ 60.186252] CPU: 0 PID: 508 Comm: pcitest Not tainted 6.0.0-rc1rpci-dev+ #237 [ 60.193387] Hardware name: Renesas Salvator-X 2nd version board based on r8a77951 (DT) [ 60.201302] pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 60.208263] pc : swiotlb_tbl_map_single+0x2c0/0x590 [ 60.213149] lr : swiotlb_map+0x88/0x1f0 [ 60.216982] sp : ffff80000a883bc0 [ 60.220292] x29: ffff80000a883bc0 x28: 0000000000000000 x27: 0000000000000000 [ 60.227430] x26: 0000000000000000 x25: ffff0004c0da20d0 x24: ffff80000a1f77c0 [ 60.234567] x23: 0000000000000002 x22: 0001000040000010 x21: 000000007a000000 [ 60.241703] x20: 0000000000200000 x19: 0000000000000000 x18: 0000000000000000 [ 60.248840] x17: 0000000000000000 x16: 0000000000000000 x15: ffff0006ff7b9180 [ 60.255977] x14: ffff0006ff7b9180 x13: 0000000000000000 x12: 0000000000000000 [ 60.263113] x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000 [ 60.270249] x8 : 0001000000000010 x7 : ffff0004c6754b20 x6 : 0000000000000000 [ 60.277385] x5 : ffff0004c0da2090 x4 : 0000000000000000 x3 : 0000000000000001 [ 60.284521] x2 : 0000000040000000 x1 : 0000000000000000 x0 : 0000000040000010 [ 60.291658] Call trace: [ 60.294100] swiotlb_tbl_map_single+0x2c0/0x590 [ 60.298629] swiotlb_map+0x88/0x1f0 [ 60.302115] dma_map_page_attrs+0x188/0x230 [ 60.306299] pci_endpoint_test_ioctl+0x5e4/0xd90 [pci_endpoint_test] [ 60.312660] __arm64_sys_ioctl+0xa8/0xf0 [ 60.316583] invoke_syscall+0x44/0x108 [ 60.320334] el0_svc_common.constprop.0+0xcc/0xf0 [ 60.325038] do_el0_svc+0x2c/0xb8 [ 60.328351] el0_svc+0x2c/0x88 [ 60.331406] el0t_64_sync_handler+0xb8/0xc0 [ 60.335587] el0t_64_sync+0x18c/0x190 [ 60.339251] Code: 52800013 d2e00414 35fff45c d503201f (d4210000) [ 60.345344] ---[ end trace 0000000000000000 ]---

To fix it, this patch adds a checking the payload length if it is zero.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 8, 2025

Last Modified

April 15, 2026

References (5)

Vendor Advisories for CVE-2022-50614(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 5.10.148 (fixes >=4.15.0)—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 rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (19 versions)
  • every version up to 5.10.148-1: fixed in 5.10.148-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 235 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 138 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2022-50614?
CVE-2022-50614 is a vulnerability whose severity is not yet rated; its CVE record was published on December 8, 2025. In the Linux kernel, the following vulnerability has been resolved: misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic The dma_map_single() doesn't permit zero length mapping. It causes a follow panic. A panic was reported on arm64: [ 60.137988] ------------[ cut here…
When was the CVE record for CVE-2022-50614 published?
The CVE record for CVE-2022-50614 was published on December 8, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2022-50614 actively exploited?
CVE-2022-50614 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2022-50614?
A fix for CVE-2022-50614 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50614 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-50614?

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

Book a Demo →Browse All CVEs