CVE-2026-99754: scsi: target: Verify the iSCSI ISID is null-terminated
In the Linux kernel, the following vulnerability has been resolved:
scsi: target: Verify the iSCSI ISID is null-terminated
iscsiparseprouttransportid() 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 corescsi3locateprreg() and in the REGISTER AND MOVE path, and snprintf("%s") in corescsi3doallocregistration(), which also reads its first 8 bytes unconditionally with getunalignedbe64() - a NUL check does not bound that read.
When the parameter list spans more than one page, transportkmapdatasg() 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 + SPECIPT 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: corescsi3locateprreg+0xd3/0x120 [targetcoremod] corescsi3decodespeciport+0x8fc/0x13a0 [targetcoremod] corescsi3emulateproregister+0x73c/0x900 [targetcoremod] ... iscsitargetrxthread+0xef/0x1d0 [iscsitargetmod]
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 prregisid, 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 prregisid[PRREGISIDLEN] 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 TCMINVALIDPARAMETERLIST; on SPECIPT no target port claims the malformed TransportID, and the command fails the same way.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1
Event History
Frequently Asked Questions
What conditions are required to trigger the fault?
An initiator must send a malformed PERSISTENT RESERVE OUT parameter list containing a FORMAT CODE 01b TransportID whose iSCSI ISID is not NUL-terminated. The described crash is reproduced when the parameter list is exactly 8192 bytes, the final TransportID contains a 12-byte unterminated ISID, and the list spans more than one page.
What is the impact of successful exploitation?
The unterminated ISID can be consumed as a C string by registration handling, causing an out-of-bounds read. When the parameter-list mapping ends at a vmalloc guard page, this results in a kernel page fault and oops.
How can I determine whether a system has encountered this issue?
Look for a kernel BUG reporting an inability to handle a page fault in conjunction with iSCSI persistent-reservation processing. The reported reproduction involves a PR OUT REGISTER + SPEC_I_PT request with an 8192-byte parameter list and a final TransportID carrying an unterminated ISID.