CVE-2026-99754scsi: target: Verify the iSCSI ISID is null-terminated
- —Not scoredno CVSS score yet
- —Exploitation in 30 daysno EPSS score yet
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 56 days later
· 56 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE.
- EPSS (exploitation in 30 days)
- Not scored
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 – < 29c5ce6465b5696fbdf8126fcd0a6946b005c8b7
- affected c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 – < 8a71f25a34439e99e094fabb619f787d15aaf9ae
- affected c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 – < d1db24c32bbe7b998573392070c3a6bdd9f4066c
- affected c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 – < cdf4b87a18cb6a0ee26865cb1b7b5660a491d302
- affected 2.6.38
- unaffected < 2.6.38
- unaffected 6.12.118 – ≤ 6.12.*
- unaffected 6.18.64 – ≤ 6.18.*
- unaffected 7.3.5 – ≤ 7.3.*
- unaffected 7.4-rc2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/29c5ce6465b5696fbdf8126fcd0a6946b005c8b7 (opens in a new tab)
- https://git.kernel.org/stable/c/8a71f25a34439e99e094fabb619f787d15aaf9ae (opens in a new tab)
- https://git.kernel.org/stable/c/d1db24c32bbe7b998573392070c3a6bdd9f4066c (opens in a new tab)
- https://git.kernel.org/stable/c/cdf4b87a18cb6a0ee26865cb1b7b5660a491d302 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99754)Record last updated .