PT-2026-152633

CVE-2026-99754

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

In the Linux kernel, the following vulnerability has been resolved:
scsi: target: Verify the iSCSI ISID is null-terminated
iscsi parse pr out transport id() returns the ISID of a FORMAT CODE 01b TransportID as a pointer into the PERSISTENT RESERVE OUT parameter list, lowercased in place and never null-terminated. spc4r37 Table 508 requires the field to be null-terminated, but a non-conforming initiator can omit the NULL; when the ISID ends at the end of the received buffer, the pointer is not a C string.
The registration code still consumes it as one: strcmp() in core scsi3 locate pr reg() and in the REGISTER AND MOVE path, and snprintf("%s") in core scsi3 do alloc registration(), which also reads its first 8 bytes unconditionally with get unaligned be64() - a NUL check does not bound that read.
When the parameter list spans more than one page, transport kmap data sg() maps it with vmap(), and the over-read walks off the end of the mapping into the vmalloc() guard page and oopses. Reproduced with a PR OUT REGISTER + SPEC I PT parameter list of exactly 8192 bytes whose final TransportID carries a 12-byte ISID without a terminating NUL:
BUG: unable to handle page fault for address: ffffc9000138c000 RIP: 0010:strcmp+0xc/0x30 Call Trace: core scsi3 locate pr reg+0xd3/0x120 [target core mod] core scsi3 decode spec i port+0x8fc/0x13a0 [target core mod] core scsi3 emulate pro register+0x73c/0x900 [target core mod] ... iscsi target rx thread+0xef/0x1d0 [iscsi target mod]
With a single-page parameter list the buffer is a kmap() direct mapping, so the over-read continues into the physically adjacent page instead of faulting. snprintf("%s") then copies whatever follows the ISID in memory into pr reg isid, and PR IN READ FULL STATUS reports the registration back to any initiator, turning the over-read into an info leak of kernel heap contents. Reproduced with a 4096-byte parameter list whose last TransportID ends at the end of the buffer with a 4-byte ISID and no NUL, interleaved with I/O to populate adjacent pages: the READ FULL STATUS response returned the ISID as "0xleak" followed by raw bytes that were not part of the parameter list. The snprintf() into pr reg isid[PR REG ISID LEN] caps the echoed ISID at 15 characters, so at most 11 bytes past the buffer are leaked per command, but the PR OUT command is not rate limited.
Any initiator that can send PR OUT to an iSCSI-exported LUN can trigger either variant, including a guest via vhost-scsi.
Require 8 bytes to remain after the ",i,0x" separator, and a NUL inside the rest of the descriptor, before the ISID pointer is returned. REGISTER AND MOVE fails with TCM INVALID PARAMETER LIST; on SPEC I PT no target port claims the malformed TransportID, and the command fails the same way.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾