GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel IB/isert (full-feature-phase PDU byte_len validation): isert_recv_done() passes received PDUs to the

CVSS 9.1CVE-2026-90414Kernel, userspace & hypervisorcurated

Impact

isert_recv_done() passes received PDUs to the opcode handlers without ever checking wc->byte_len, the count of bytes the HCA actually placed in the receive descriptor. isert_handle_iscsi_dataout() and isert_handle_scsi_cmd() then copy the initiator-declared data-segment length out of that fixed ISER_RX_SIZE descriptor, so an initiator that declares more than it sent over-reads the receive buffer. The immediate-data path is worse than a read: it aliases the descriptor via sg_set_buf() and hands it to the backend as the source of a SCSI WRITE, so kernel heap past the descriptor is written through to the backing store. Nothing upstream closes this - the target core bounds the inbound payload against MaxXmitDataSegmentLength, which is derived from a value the initiator declares verbatim, and isert never clamps it to its own descriptor size. For an operator, a host on the storage fabric can corrupt data at rest on a shared target and crash the node that serves it.

Who can reach it

An initiator that has completed login on the iSER/RDMA target - full feature phase - having declared a large TargetRecvDataSegmentLength and a FirstBurstLength that permits immediate or unsolicited data. Post-authentication, unlike CVE-2026-90413 in the login path of the same driver.

What to do

Move target nodes onto a stable kernel that validates wc->byte_len against the declared framing before the handlers copy. That is a drain and reboot per node. Until then treat the set of initiators permitted to log in to the target as the security boundary, and check backing-store integrity if you suspect an initiator has been abusing it. The record links the stable commits for backporting.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.