CVE-2022-50543

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-10-07. NVD baseline CVSS 7.8; sources differ by 0.0.

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

A fix is available — apply it.

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

RDMA/rxe: Fix mr->map double free

rxe_mr_cleanup() which tries to free mr->map again will be called when rxe_mr_init_user() fails:

CPU: 0 PID: 4917 Comm: rdma_flush_serv Kdump: loaded Not tainted 6.1.0-rc1-roce-flush+ #25 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 Call Trace: dump_stack_lvl+0x45/0x5d panic+0x19e/0x349 end_report.part.0+0x54/0x7c kasan_report.cold+0xa/0xf rxe_mr_cleanup+0x9d/0xf0 [rdma_rxe] __rxe_cleanup+0x10a/0x1e0 [rdma_rxe] rxe_reg_user_mr+0xb7/0xd0 [rdma_rxe] ib_uverbs_reg_mr+0x26a/0x480 [ib_uverbs] ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x1a2/0x250 [ib_uverbs] ib_uverbs_cmd_verbs+0x1397/0x15a0 [ib_uverbs]

This issue was firstly exposed since commit b18c7da63fcb ("RDMA/rxe: Fix memory leak in error path code") and then we fixed it in commit 8ff5f5d9d8cf ("RDMA/rxe: Prevent double freeing rxe_map_set()") but this fix was reverted together at last by commit 1e75550648da (Revert "RDMA/rxe: Create duplicate mapping tables for FMRs")

Simply let rxe_mr_cleanup() always handle freeing the mr->map once it is successfully allocated.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

October 7, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

RDMA/rxe: Fix mr->map double free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d984dac8f6bf4ebd3398af82b357e1d181ecaac
generic

RDMA/rxe: Fix mr->map double free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ce577f09013206e36e674cd27da3707b2278268
generic

RDMA/rxe: Fix mr->map double free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06f73568f553b5be6ba7f6fe274d333ea29fc46d

Vendor Advisories for CVE-2022-50543(6)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-372.175.1.el8_62026-01-14redhat
redhatkernel-0:4.18.0-477.124.1.el8_82026-01-14redhat
redhatkernel-rt-0:4.18.0-553.89.1.rt7.430.el8_102025-12-08redhat
redhatkernel-0:4.18.0-553.89.1.el8_102025-12-08redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
redhatkernel-0:4.18.0-477.10.1.el8_82023-05-16redhat
linuxKernel @ 6.0.16—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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.4-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 26× 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 150 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-50543?
CVE-2022-50543 is a high vulnerability published on October 7, 2025. In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix mr->map double free rxemrcleanup() which tries to free mr->map again will be called when rxemrinit_user() fails: CPU: 0 PID: 4917 Comm: rdmaflushserv Kdump: loaded Not tainted 6.1.0-rc1-roce-flush+ #25 Hardware name:…
When was CVE-2022-50543 disclosed?
CVE-2022-50543 was first published in the National Vulnerability Database on October 7, 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-50543 actively exploited?
CVE-2022-50543 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.3% of all scored CVEs.
What is the CVSS score of CVE-2022-50543?
CVE-2022-50543 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50543?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50543, 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-50543

Explore →

Is Your Infrastructure Affected by CVE-2022-50543?

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

Start Free Scan →Browse All CVEs