CVE-2026-46133

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
43.5%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 24, 2026

Advisory Details (8)

Auto-updated Jun 7, 2026
No patch confirmed yet.
generic

RDMA/rxe: Reject unknown opcodes before ICRC processing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8ee926431a7bbec2b10c1290664af2cb290b983
generic

RDMA/rxe: Reject unknown opcodes before ICRC processing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e3dc3a2fb05f4ed49c7f20594c4c52350d032189
generic

RDMA/rxe: Reject unknown opcodes before ICRC processing - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/rxe: Reject unknown opcodes before ICRC processing - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/rxe: Reject unknown opcodes before ICRC processing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/599cfdf44c1701c581cd4a21f1e1e03f8dc3840b
generic

RDMA/rxe: Reject unknown opcodes before ICRC processing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c6f86d85d03cdb33addce86aa69aa795ca6c47a
generic

RDMA/rxe: Reject unknown opcodes before ICRC processing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/318787fa7193bd79691f2ebce4e80cb6abd0faef
generic

RDMA/rxe: Reject unknown opcodes before ICRC processing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/006a3a5f75345c6a0dbf13fd3ee01406e93b6733

Vendor Advisories for CVE-2026-46133(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-46133?
CVE-2026-46133 is a high vulnerability published on May 28, 2026. 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 payloadsize() in rxercv"), a single unauthenticated UDP packet can still trigger panic. That…
When was CVE-2026-46133 disclosed?
CVE-2026-46133 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46133 actively exploited?
CVE-2026-46133 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 43.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46133?
CVE-2026-46133 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-46133?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46133, 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

Explore the affected products and dependency analysis for CVE-2026-46133

Explore →

Is Your Infrastructure Affected by CVE-2026-46133?

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