CVE-2026-99302 in Linuxinfo

Summary

by MITRE • 11/16/2026

In the Linux kernel, the following vulnerability has been resolved:

nvmet-rdma: reject short connection requests

nvmet_rdma_parse_cm_connect_req() treats RDMA-CM private data as a struct nvme_rdma_cm_req but accepts any nonzero private_data_len. The iWARP path allocates exactly the peer-provided length, so a six-byte MPA request reaches the parser and the hsqsize load reads two bytes past the allocation.

Require the complete request structure before reading any of its fields. The decoded KASAN report is:

BUG: KASAN: slab-out-of-bounds in nvmet_rdma_cm_handler (drivers/nvme/target/rdma.c:1427 drivers/nvme/target/rdma.c:1475 drivers/nvme/target/rdma.c:1614 drivers/nvme/target/rdma.c:1814) Read of size 2 at addr ff1100010459d366 by task kworker/u16:1/41 Workqueue: iw_cm_wq cm_work_handler Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) print_report (mm/kasan/report.c:378 mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:595) nvmet_rdma_cm_handler (drivers/nvme/target/rdma.c:1427 drivers/nvme/target/rdma.c:1475 drivers/nvme/target/rdma.c:1614 drivers/nvme/target/rdma.c:1814) cma_cm_event_handler (drivers/infiniband/core/cma.c:2181) iw_conn_req_handler (drivers/infiniband/core/cma.c:2640) cm_work_handler (drivers/infiniband/core/cm.c:2502 drivers/infiniband/core/cm.c:3858) process_one_work (kernel/workqueue.c:3396) worker_thread (kernel/workqueue.c:3479 kernel/workqueue.c:3560) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) </TASK>

Allocated by task 12: __kasan_kmalloc (mm/kasan/common.c:398 mm/kasan/common.c:415) __kmalloc_node_track_caller_noprof (mm/slub.c:5414 mm/slub.c:5545) kmemdup_noprof (mm/util.c:138) cm_event_handler (drivers/infiniband/core/iwcm.c:194 drivers/infiniband/core/iwcm.c:1076) siw_cm_upcall (drivers/infiniband/sw/siw/siw_cm.c:408) siw_proc_mpareq (drivers/infiniband/sw/siw/siw_cm.c:750) siw_cm_work_handler (drivers/infiniband/sw/siw/siw_cm.c:1086)

The buggy address is located 0 bytes to the right of allocated 6-byte region [ff1100010459d360, ff1100010459d366)

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/16/2026

The Linux kernel vulnerability identified in the nvmet-rdma subsystem represents a critical out-of-bounds read condition arising from insufficient validation of input data lengths during RDMA connection establishment. Specifically, the function nvmet_rdma_parse_cm_connect_req is responsible for parsing private data associated with an RDMA Connection Manager connect request. The core flaw lies in the fact that this routine treats the incoming private data buffer as a struct nvme_rdma_cm_req structure but fails to verify that the provided length matches or exceeds the size of said structure. Instead, it accepts any nonzero value for private_data_len and proceeds to access fields within the structure without bounds checking. This design oversight creates a scenario where malformed or truncated connection requests can trigger memory safety violations when processed by the kernel.

The operational impact is most severe in environments utilizing iWARP protocols, as indicated by the KASAN report details. In an iWARP implementation, the system allocates memory for the private data based strictly on the length provided by the peer during the handshake phase. If a remote attacker sends a maliciously crafted MPA request with a short payload, such as one containing only six bytes of private data, the kernel will allocate exactly that amount of space. However, when nvmet_rdma_parse_cm_connect_req attempts to read fields from this buffer assuming it contains a full struct nvme_rdma_cm_req, it inevitably reads beyond the allocated boundary. The specific instance documented in the KASAN trace shows an attempt to load two bytes for the hsqsize field at an address located immediately after the end of the six-byte allocation region. This constitutes a slab-out-of-bounds read error, which is classified under CWE-125: Out-of-bounds Read.

From a security perspective, this vulnerability allows for potential information disclosure or denial of service conditions depending on how the kernel handles the invalid memory access and whether KASAN protections are active in production environments. While modern kernels often include mitigations like KASAN that detect such errors and panic to prevent exploitation, the underlying flaw remains dangerous because it violates fundamental memory safety principles. An attacker could potentially leverage this out-of-bounds read to leak sensitive kernel stack or heap contents if adjacent memory contains confidential data. Furthermore, consistent triggering of these faults can lead to system instability or crashes, impacting availability. This behavior aligns with ATT&CK technique T1083: File and Directory Discovery, as the attacker may be attempting to enumerate internal state information through side-channel effects caused by reading unintended memory regions during connection setup procedures.

The resolution involves enforcing strict length validation before any structural fields are accessed. By requiring that the private_data_len is at least equal to sizeof(struct nvme_rdma_cm_req), the kernel ensures that all subsequent reads remain within the bounds of the allocated buffer. This fix prevents the out-of-bounds access by rejecting connection requests that do not carry sufficient data to populate the expected structure fields completely. Administrators and developers should ensure that their Linux kernels are updated with this patch applied, particularly in systems exposing NVMe over RDMA services to untrusted networks. Regular auditing of network-facing kernel modules for similar input validation gaps is recommended to maintain robust security postures against protocol-level attacks targeting remote management interfaces.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!