nday
CVE-2026-99302

nvmet-rdma: reject short connection requests

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
11-16T09:59Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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)

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , observed live · raw
{
  "id": 472528,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-99302",
  "occurred_at": "2026-11-16T09:59:27.815Z",
  "observed_at": "2026-11-16T11:01:30.441316Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2026-11-16T09:59:27.815Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.