Bug 2482550 (CVE-2026-46133) - CVE-2026-46133 kernel: RDMA/rxe: Reject unknown opcodes before ICRC processing
Summary: CVE-2026-46133 kernel: RDMA/rxe: Reject unknown opcodes before ICRC processing
Keywords:
Status: NEW
Alias: CVE-2026-46133
Product: Security Response
Classification: Other
Component: vulnerability-draft
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-28 11:02 UTC by OSIDB Bzimport
Modified: 2026-10-29 14:18 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:68570 0 None None None 2026-09-17 12:15:48 UTC
Red Hat Product Errata RHSA-2026:70402 0 None None None 2026-09-22 20:21:04 UTC
Red Hat Product Errata RHSA-2026:70403 0 None None None 2026-09-22 19:30:15 UTC
Red Hat Product Errata RHSA-2026:77216 0 None None None 2026-10-07 02:49:13 UTC
Red Hat Product Errata RHSA-2026:77217 0 None None None 2026-10-07 03:39:03 UTC
Red Hat Product Errata RHSA-2026:77218 0 None None None 2026-10-07 06:27:31 UTC
Red Hat Product Errata RHSA-2026:77219 0 None None None 2026-10-08 07:23:20 UTC
Red Hat Product Errata RHSA-2026:77301 0 None None None 2026-10-07 07:05:00 UTC

Description OSIDB Bzimport 2026-05-28 11:02:51 UTC
In the Linux kernel, the following vulnerability has been resolved:

RDMA/rxe: Reject unknown opcodes before ICRC processing

Even after applying commit 7244491dab34 ("RDMA/rxe: Validate pad and ICRC
before payload_size() in rxe_rcv"), a single unauthenticated UDP packet
can still trigger panic.  That patch handled payload_size() underflow only
for valid opcodes with short packets, not for packets carrying an unknown
opcode.  The unknown-opcode OOB read described below predates that commit
and reaches back to the initial Soft RoCE driver.

The check added there reads

    pkt->paylen < header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE

where header_size(pkt) expands to rxe_opcode[pkt->opcode].length.  The
rxe_opcode[] array has 256 entries but is only populated for defined IB
opcodes; any other entry (for example opcode 0xff) is zero-initialized, so
length == 0 and the check degenerates to

    pkt->paylen < 0 + bth_pad(pkt) + RXE_ICRC_SIZE

which does not constrain pkt->paylen enough.  rxe_icrc_hdr() then computes

    rxe_opcode[pkt->opcode].length - RXE_BTH_BYTES

which underflows when length == 0 and passes a huge value to rxe_crc32(),
causing an out-of-bounds read of the skb payload.

Reproduced on v7.0-rc7 with that fix applied, QEMU/KVM with
CONFIG_RDMA_RXE=y and CONFIG_KASAN=y, after

    rdma link add rxe0 type rxe netdev eth0

A single 48-byte UDP packet to port 4791 with BTH opcode=0xff and
QPN=IB_MULTICAST_QPN triggers:

    BUG: KASAN: slab-out-of-bounds in crc32_le+0x115/0x170
    Read of size 1 at addr ...
    The buggy address is located 0 bytes to the right of
     allocated 704-byte region
    Call Trace:
     crc32_le+0x115/0x170
     rxe_icrc_hdr.isra.0+0x226/0x300
     rxe_icrc_check+0x13f/0x3a0
     rxe_rcv+0x6e1/0x16e0
     rxe_udp_encap_recv+0x20a/0x320
     udp_queue_rcv_one_skb+0x7ed/0x12c0

Subsequent packets with the same shape fault on unmapped memory and panic
the kernel.  The trigger requires only module load and "rdma link add"; no
QP, no connection, and no authentication.

Fix this by rejecting packets whose opcode has no rxe_opcode[] entry,
detected via the zero mask or zero length, before any length arithmetic
runs.

Comment 4 Jon Orris 2026-09-17 12:15:47 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:68570 https://access.redhat.com/errata/RHSA-2026:68570

Comment 5 Jon Orris 2026-09-22 19:30:14 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:70403 https://access.redhat.com/errata/RHSA-2026:70403

Comment 6 Jon Orris 2026-09-22 20:21:04 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:70402 https://access.redhat.com/errata/RHSA-2026:70402

Comment 8 Jon Orris 2026-10-07 02:49:12 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On

Via RHSA-2026:77216 https://access.redhat.com/errata/RHSA-2026:77216

Comment 9 Jon Orris 2026-10-07 03:39:02 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On

Via RHSA-2026:77217 https://access.redhat.com/errata/RHSA-2026:77217

Comment 10 Jon Orris 2026-10-07 06:27:29 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions

Via RHSA-2026:77218 https://access.redhat.com/errata/RHSA-2026:77218

Comment 11 Jon Orris 2026-10-07 07:04:59 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.8 Telecommunications Update Service

Via RHSA-2026:77301 https://access.redhat.com/errata/RHSA-2026:77301

Comment 12 Jon Orris 2026-10-08 07:23:19 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:77219 https://access.redhat.com/errata/RHSA-2026:77219


Note You need to log in before you can comment on or make changes to this bug.