CVE-2026-46043Critical· 9.1▾ MidnightIn the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long befor…
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 50.1 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.5%
Last analysed / modified upstream
In the Linux kernel, the following vulnerability has been resolved:
RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv
rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long before payload_size() is used.
However, payload_size() subtracts both the attacker-controlled BTH pad field and RXE_ICRC_SIZE from pkt->paylen:
payload_size = pkt->paylen - offset[RXE_PAYLOAD] - bth_pad(pkt) - RXE_ICRC_SIZE
This means a short packet can still make payload_size() underflow even if it includes enough bytes for the fixed headers. Simply requiring header_size(pkt) + RXE_ICRC_SIZE is not sufficient either, because a packet with a forged non-zero BTH pad can still leave payload_size() negative and pass an underflowed value to later receive-path users.
Fix this by validating pkt->paylen against the full minimum length required by payload_size(): header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE.
Linux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < c4376c672c3648d5bdc31dfffc329d07164f93c4Linux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < 5fedefec757192dcaad29a664ac332c7601be144Linux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < 2c0d71ef12f46c57d37bc571f3f2797db7eb50ccLinux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < 2fd4f8b749309a61c3f3f88ee8891d94f79e1240Linux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < f83519a4c122c9c7a850a2197648a9ff4c67c520Linux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < 9b924f3a26b21330a837cfe72e819b6393bbeeaaLinux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < e8ee0e792d475b1067c199ef0af1b6221fa6f43dLinux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 < 7244491dab347f648e661da96dc0febadd9daec3Linux 4.8Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets