Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-45852: RDMA/rxe: Fix double free in rxe_srq_from_init

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.19% (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 0beefd0e15d962f497aad750b2d5e9c3570b66d1, 26793db60925df1e88a29466813d586cbc190b8c, 26a9cfe12f4ffdeaa136f252478986fa5f397ddc.

Low priority for now. Upgrade to Linux Linux 0beefd0e15d962f497aad750b2d5e9c3570b66d1, 26793db60925df1e88a29466813d586cbc190b8c, 26a9cfe12f4ffdeaa136f252478986fa5f397ddc 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 double free in rxe_srq_from_init In rxe_srq_from_init(), the queue pointer 'q' is assigned to 'srq->rq.queue' before copying the SRQ number to user space. If copy_to_user() fails, the function calls rxe_queue_cleanup() to free the queue, but leaves the now-invalid pointer in 'srq->rq.queue'. The caller of rxe_srq_from_init() (rxe_create_srq) eventually calls rxe_srq_cleanup() upon receiving the error, which triggers a second rxe_queue_cleanup() on the same memory, leading to a double free. The call trace looks like this: kmem_cache_free+0x.../0x... rxe_queue_cleanup+0x1a/0x30 [rdma_rxe] rxe_srq_cleanup+0x42/0x60 [rdma_rxe] rxe_elem_release+0x31/0x70 [rdma_rxe] rxe_create_srq+0x12b/0x1a0 [rdma_rxe] ib_create_srq_user+0x9a/0x150 [ib_core] Fix this by moving 'srq->rq.queue = q' after copy_to_user.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 27, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 9th 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
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

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-2026-45852

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 kernel4.19.86 and later · before 5.10.259
  • linux linux kernel5.11 and later · before 5.15.210
  • linux linux kernel5.16 and later · before 6.1.176
  • linux linux kernel6.2 and later · before 6.6.128
  • linux linux kernel6.7 and later · before 6.12.75
  • linux linux kernel6.13 and later · before 6.18.14
  • linux linux kernel6.19 and later · before 6.19.4

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

    • 350703fae672d4d649c3562c199eab5ec9dc7c79, 4.20affected
    • aae0484e15f062ad2c2502e68e15dfb8b8f84608 and later · before b98ab5494dbd48652561aa0b9c32f10500220745affected · git
    • aae0484e15f062ad2c2502e68e15dfb8b8f84608 and later · before d493e0bfc748a520c349d6c8791b262aa5ad2e4eaffected · git
    • aae0484e15f062ad2c2502e68e15dfb8b8f84608 and later · before 9abff51163aa1bc275ec356f74fe976291860a7faffected · git
    • aae0484e15f062ad2c2502e68e15dfb8b8f84608 and later · before 26793db60925df1e88a29466813d586cbc190b8caffected · git
    • aae0484e15f062ad2c2502e68e15dfb8b8f84608 and later · before ce6f8e007682f378279d4cf83b240f12d52c723baffected · git
    • aae0484e15f062ad2c2502e68e15dfb8b8f84608 and later · before 5c07aef09a121a4cd622a71eb0753a9e135c84a8affected · git
    • aae0484e15f062ad2c2502e68e15dfb8b8f84608 and later · before 26a9cfe12f4ffdeaa136f252478986fa5f397ddcaffected · git
    • aae0484e15f062ad2c2502e68e15dfb8b8f84608 and later · before 0beefd0e15d962f497aad750b2d5e9c3570b66d1affected · git
    • 4.19.86 and later · before 4.20affected · semver

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.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.132.1.el8_104.18.0-553.132.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.132.1.rt7.473.el8_104.18.0-553.132.1.rt7.473.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.132.1.rt7.473.el8_104.18.0-553.132.1.rt7.473.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.132.1.rt7.473.el8_104.18.0-553.132.1.rt7.473.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.132.1.rt7.473.el8_104.18.0-553.132.1.rt7.473.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.132.1.rt7.473.el8_104.18.0-553.132.1.rt7.473.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.132.1.rt7.473.el8_104.18.0-553.132.1.rt7.473.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.132.1.rt7.473.el8_104.18.0-553.132.1.rt7.473.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.132.1.rt7.473.el8_104.18.0-553.132.1.rt7.473.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.132.1.rt7.473.el8_104.18.0-553.132.1.rt7.473.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-2025-71312May 27, 2026 · fs/ntfs3: fix ntfs_mount_options leak in ntfs_fill_super()
    22Monitor
  • ← EarlierCVE-2026-45850May 27, 2026 · ipvs: skip ipv6 extension headers for csum checks
    22Monitor
  • Later →CVE-2026-45856May 27, 2026 · RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send
    28Monitor

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 Linux0beefd0e15d962f497aad750b2d5e9c3570b66d1Vendor (CNA)
Linux Linux26793db60925df1e88a29466813d586cbc190b8cVendor (CNA)
Linux Linux26a9cfe12f4ffdeaa136f252478986fa5f397ddcVendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux5c07aef09a121a4cd622a71eb0753a9e135c84a8Vendor (CNA)
Linux Linux9abff51163aa1bc275ec356f74fe976291860a7fVendor (CNA)
Linux Linuxb98ab5494dbd48652561aa0b9c32f10500220745Vendor (CNA)
Linux Linuxce6f8e007682f378279d4cf83b240f12d52c723bVendor (CNA)
Linux Linuxd493e0bfc748a520c349d6c8791b262aa5ad2e4eVendor (CNA)
almalinux:bpftool4.18.0-553.132.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.132.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.132.1.rt7.473.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.132.1.rt7.473.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.132.1.rt7.473.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.132.1.rt7.473.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.132.1.rt7.473.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.132.1.rt7.473.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.132.1.rt7.473.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:4.18.0-553.132.1.rt7.473.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)

+18

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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-4341419 days apartscsi: qla2xxx: Completely fix fcport double free
    39Monitor
  • CVE-2026-4301126 days apartnet/x25: Fix potential double free of skb
    39Monitor
  • CVE-2026-5299328 days aparttipc: fix double-free in tipc_buf_append()
    39Monitor
  • CVE-2026-3160833 days apartsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()
    39Monitor
  • CVE-2026-3160933 days apartsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()
    39Monitor
  • CVE-2026-6438659 days apartsmb: client: fix query_info() replay double-free
    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-secondary

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. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

All records