Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50543: RDMA/rxe: Fix mr->map double free

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 06f73568f553b5be6ba7f6fe274d333ea29fc46d, 5.20, 6ce577f09013206e36e674cd27da3707b2278268.

Low priority for now. Upgrade to Linux Linux 06f73568f553b5be6ba7f6fe274d333ea29fc46d, 5.20, 6ce577f09013206e36e674cd27da3707b2278268 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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: <TASK> 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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Oct 7, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-50543

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.19.4 and later · before 6.0.16
  • linux linux kernel6.1 and later · before 6.1.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • e004a35e8148ad9fc438b0479884641acf382896, 6.0affected
    • 1e75550648da1fa1cd1969e7597355de8fe8caf6 and later · before 6ce577f09013206e36e674cd27da3707b2278268affected · git
    • 1e75550648da1fa1cd1969e7597355de8fe8caf6 and later · before 06f73568f553b5be6ba7f6fe274d333ea29fc46daffected · git
    • 1e75550648da1fa1cd1969e7597355de8fe8caf6 and later · before 7d984dac8f6bf4ebd3398af82b357e1d181ecaacaffected · git
    • 5.19.4 and later · before 5.20affected · semver
    • before 6.0not affected · semver
    • 6.0.16 and later · up to and including 6.0.*not affected · semver
    • 6.1.2 and later · up to and including 6.1.*not affected · semver
    • 6.2 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.89.1.el8_104.18.0-553.89.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.89.1.rt7.430.el8_104.18.0-553.89.1.rt7.430.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.89.1.rt7.430.el8_104.18.0-553.89.1.rt7.430.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.89.1.rt7.430.el8_104.18.0-553.89.1.rt7.430.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.89.1.rt7.430.el8_104.18.0-553.89.1.rt7.430.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.89.1.rt7.430.el8_104.18.0-553.89.1.rt7.430.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.89.1.rt7.430.el8_104.18.0-553.89.1.rt7.430.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.89.1.rt7.430.el8_104.18.0-553.89.1.rt7.430.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.89.1.rt7.430.el8_104.18.0-553.89.1.rt7.430.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.89.1.rt7.430.el8_104.18.0-553.89.1.rt7.430.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-50541Oct 7, 2025 · dmaengine: ti: k3-udma: Reset UDMA_CHAN_RT byte counters to prevent overflow
    22Monitor
  • ← EarlierCVE-2022-50542Oct 7, 2025 · media: si470x: Fix use-after-free in si470x_int_in_callback()
    31Monitor
  • Later →CVE-2022-50545Oct 7, 2025 · r6040: Fix kmemleak in probe and remove
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux06f73568f553b5be6ba7f6fe274d333ea29fc46dVendor (CNA)
Linux Linux5.20Vendor (CNA)
Linux Linux6ce577f09013206e36e674cd27da3707b2278268Vendor (CNA)
Linux Linux7d984dac8f6bf4ebd3398af82b357e1d181ecaacVendor (CNA)
almalinux:bpftool4.18.0-553.89.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.89.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.89.1.rt7.430.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.89.1.rt7.430.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.89.1.rt7.430.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.89.1.rt7.430.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.89.1.rt7.430.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.89.1.rt7.430.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.89.1.rt7.430.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.89.1.rt7.430.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.89.1.rt7.430.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.89.1.rt7.430.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules-extra0:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo0:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo-common-x86_640:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-devel0:4.18.0-553.89.1.rt7.430.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
rocky linux:kernel0:4.18.0-553.89.1.el8_10 · Rocky Linux:8Package registry (OSV)

+1

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-31608199 days apartsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()
    39Monitor
  • CVE-2026-31609199 days apartsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()
    39Monitor
  • CVE-2026-43011206 days apartnet/x25: Fix potential double free of skb
    39Monitor
  • CVE-2026-43414213 days apartscsi: qla2xxx: Completely fix fcport double free
    39Monitor
  • CVE-2026-52993260 days aparttipc: fix double-free in tipc_buf_append()
    39Monitor
  • CVE-2026-63888285 days apartscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()
    39Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-415 · Double Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records