CVE-2026-46133

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 5, 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.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.186.196~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-25ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-25ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-25ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-25ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.88-1~bpo12+1 (21 versions)6.12.88-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 90× 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 294 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 04:55 UTCEG score recompute
  11. 2026-08-25 04:55 UTCVendor advisory
  12. 2026-08-25 04:55 UTCGHSA enrichment
  13. 2026-08-23 14:44 UTCEG score recompute
  14. 2026-08-23 14:44 UTCVendor advisory
  15. 2026-08-23 14:44 UTCGHSA enrichment
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-21 15:54 UTCEG score recompute
  19. 2026-08-21 15:54 UTCVendor advisory
  20. 2026-08-21 15:53 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 22:31 UTCVendor advisory
  23. 2026-08-20 22:31 UTCGHSA enrichment
  24. 2026-08-20 11:01 UTCEG score recompute
  25. 2026-08-20 11:01 UTCVendor advisory
Show 75 more
  1. 2026-08-20 11:01 UTCGHSA enrichment
  2. 2026-08-19 17:04 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 09:00 UTCVendor advisory
  6. 2026-08-17 09:00 UTCGHSA enrichment
  7. 2026-08-16 15:11 UTCEG score recompute
  8. 2026-08-16 15:11 UTCVendor advisory
  9. 2026-08-16 15:11 UTCGHSA enrichment
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 02:40 UTCEG score recompute
  12. 2026-08-16 02:40 UTCVendor advisory
  13. 2026-08-16 02:40 UTCGHSA enrichment
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 23:33 UTCVendor advisory
  17. 2026-08-14 23:33 UTCGHSA enrichment
  18. 2026-08-14 12:27 UTCVendor advisory
  19. 2026-08-14 12:27 UTCGHSA enrichment
  20. 2026-08-14 01:21 UTCEG score recompute
  21. 2026-08-14 01:21 UTCVendor advisory
  22. 2026-08-14 01:21 UTCGHSA enrichment
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 08:02 UTCVendor advisory
  25. 2026-08-13 08:02 UTCGHSA enrichment
  26. 2026-08-12 20:38 UTCEG score recompute
  27. 2026-08-12 20:38 UTCVendor advisory
  28. 2026-08-12 20:38 UTCGHSA enrichment
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-12 09:32 UTCVendor advisory
  31. 2026-08-12 09:32 UTCGHSA enrichment
  32. 2026-08-11 22:26 UTCEG score recompute
  33. 2026-08-11 22:26 UTCVendor advisory
  34. 2026-08-11 22:25 UTCGHSA enrichment
  35. 2026-08-11 11:19 UTCVendor advisory
  36. 2026-08-11 11:19 UTCGHSA enrichment
  37. 2026-08-11 00:07 UTCEG score recompute
  38. 2026-08-11 00:07 UTCVendor advisory
  39. 2026-08-11 00:07 UTCGHSA enrichment
  40. 2026-08-11 00:00 UTCEPSS rescore
  41. 2026-08-10 06:14 UTCVendor advisory
  42. 2026-08-10 06:14 UTCGHSA enrichment
  43. 2026-08-09 19:09 UTCEG score recompute
  44. 2026-08-09 19:09 UTCVendor advisory
  45. 2026-08-09 19:09 UTCGHSA enrichment
  46. 2026-08-09 13:46 UTCEPSS rescore
  47. 2026-08-09 08:03 UTCVendor advisory
  48. 2026-08-09 08:03 UTCGHSA enrichment
  49. 2026-08-08 20:57 UTCEG score recompute
  50. 2026-08-08 20:57 UTCVendor advisory
  51. 2026-08-08 20:57 UTCGHSA enrichment
  52. 2026-08-08 16:37 UTCEPSS rescore
  53. 2026-08-08 09:26 UTCVendor advisory
  54. 2026-08-08 09:26 UTCGHSA enrichment
  55. 2026-08-07 22:20 UTCEG score recompute
  56. 2026-08-07 22:20 UTCVendor advisory
  57. 2026-08-07 22:20 UTCGHSA enrichment
  58. 2026-08-07 11:14 UTCVendor advisory
  59. 2026-08-07 11:14 UTCGHSA enrichment
  60. 2026-08-07 00:09 UTCEG score recompute
  61. 2026-08-07 00:09 UTCVendor advisory
  62. 2026-08-07 00:09 UTCGHSA enrichment
  63. 2026-08-06 13:47 UTCEPSS rescore
  64. 2026-08-06 11:53 UTCVendor advisory
  65. 2026-08-06 11:53 UTCGHSA enrichment
  66. 2026-08-06 00:47 UTCEG score recompute
  67. 2026-08-06 00:47 UTCVendor advisory
  68. 2026-08-06 00:47 UTCGHSA enrichment
  69. 2026-08-05 19:17 UTCEPSS rescore
  70. 2026-08-05 13:41 UTCEG score recompute
  71. 2026-08-05 13:41 UTCVendor advisory
  72. 2026-08-05 13:41 UTCGHSA enrichment
  73. 2026-08-04 15:10 UTCEPSS rescore
  74. 2026-08-04 10:39 UTCEPSS rescore
  75. 2026-08-04 03:22 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 August 5, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 54.8% of all scored CVEs.
What is the CVSS score of CVE-2026-46133?
CVE-2026-46133 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.