← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-46043

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-46043

Key Details

CVECVE-2026-46043
CVSS Score / Version
9.1 (Critical) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is none; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-46043
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-46043
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.