Review reviewHigh

CVE-2026-45852

Linux Linux, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8

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

CVSS
7.8
EPSS
0.18%
7.15% percentile
CISA KEV
Not listed
Published
2026.05.27
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.18%
Technical severityCVSS 7.8

Vulnerability overview

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

Affected product and versions

Product
Linux Linux, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8
Affected versions
>= aae0484e15f062ad2c2502e68e15dfb8b8f84608 < b98ab5494dbd48652561aa0b9c32f10500220745, >= aae0484e15f062ad2c2502e68e15dfb8b8f84608 < d493e0bfc748a520c349d6c8791b262aa5ad2e4e, >= aae0484e15f062ad2c2502e68e15dfb8b8f84608 < 9abff51163aa1bc275ec356f74fe976291860a7f, >= aae0484e15f062ad2c2502e68e15dfb8b8f84608 < 26793db60925df1e88a29466813d586cbc190b8c, >= aae0484e15f062ad2c2502e68e15dfb8b8f84608 < ce6f8e007682f378279d4cf83b240f12d52c723b, >= aae0484e15f062ad2c2502e68e15dfb8b8f84608 < 5c07aef09a121a4cd622a71eb0753a9e135c84a8, >= aae0484e15f062ad2c2502e68e15dfb8b8f84608 < 26a9cfe12f4ffdeaa136f252478986fa5f397ddc, >= aae0484e15f062ad2c2502e68e15dfb8b8f84608 < 0beefd0e15d962f497aad750b2d5e9c3570b66d1, >= 350703fae672d4d649c3562c199eab5ec9dc7c79, >= 4.19.86 < 4.20, >= 4.20, >= 4.19.86 < 5.10.259, >= 5.11 < 5.15.210, >= 5.16 < 6.1.176, >= 6.2 < 6.6.128, >= 6.7 < 6.12.75, >= 6.13 < 6.18.14, >= 6.19 < 6.19.4
Fixed versions
5.10.259, 5.15.210, 6.1.176, 6.6.128, 6.12.75, 6.18.14, 6.19.4

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

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