FKIE_CVE-2026-99754
Vulnerability from fkie_nvd - Published: 2026-11-20 06:18 - Updated: 2026-11-20 06:18| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/target/target_core_fabric_lib.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "29c5ce6465b5696fbdf8126fcd0a6946b005c8b7",
"status": "affected",
"version": "c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5",
"versionType": "git"
},
{
"lessThan": "8a71f25a34439e99e094fabb619f787d15aaf9ae",
"status": "affected",
"version": "c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5",
"versionType": "git"
},
{
"lessThan": "d1db24c32bbe7b998573392070c3a6bdd9f4066c",
"status": "affected",
"version": "c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5",
"versionType": "git"
},
{
"lessThan": "cdf4b87a18cb6a0ee26865cb1b7b5660a491d302",
"status": "affected",
"version": "c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/target/target_core_fabric_lib.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.38"
},
{
"lessThan": "2.6.38",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Verify the iSCSI ISID is null-terminated\n\niscsi_parse_pr_out_transport_id() returns the ISID of a FORMAT CODE 01b\nTransportID as a pointer into the PERSISTENT RESERVE OUT parameter list,\nlowercased in place and never null-terminated. spc4r37 Table 508 requires\nthe field to be null-terminated, but a non-conforming initiator can omit\nthe NULL; when the ISID ends at the end of the received buffer, the pointer\nis not a C string.\n\nThe registration code still consumes it as one: strcmp() in\n__core_scsi3_locate_pr_reg() and in the REGISTER AND MOVE path, and\nsnprintf(\"%s\") in __core_scsi3_do_alloc_registration(), which also reads\nits first 8 bytes unconditionally with get_unaligned_be64() - a NUL check\ndoes not bound that read.\n\nWhen the parameter list spans more than one page, transport_kmap_data_sg()\nmaps it with vmap(), and the over-read walks off the end of the mapping\ninto the vmalloc() guard page and oopses. Reproduced with a PR OUT\nREGISTER + SPEC_I_PT parameter list of exactly 8192 bytes whose final\nTransportID carries a 12-byte ISID without a terminating NUL:\n\n BUG: unable to handle page fault for address: ffffc9000138c000\n RIP: 0010:strcmp+0xc/0x30\n Call Trace:\n __core_scsi3_locate_pr_reg+0xd3/0x120 [target_core_mod]\n core_scsi3_decode_spec_i_port+0x8fc/0x13a0 [target_core_mod]\n core_scsi3_emulate_pro_register+0x73c/0x900 [target_core_mod]\n ...\n iscsi_target_rx_thread+0xef/0x1d0 [iscsi_target_mod]\n\nWith a single-page parameter list the buffer is a kmap() direct mapping, so\nthe over-read continues into the physically adjacent page instead of\nfaulting. snprintf(\"%s\") then copies whatever follows the ISID in memory\ninto pr_reg_isid, and PR IN READ FULL STATUS reports the registration back\nto any initiator, turning the over-read into an info leak of kernel heap\ncontents. Reproduced with a 4096-byte parameter list whose last\nTransportID ends at the end of the buffer with a 4-byte ISID and no NUL,\ninterleaved with I/O to populate adjacent pages: the READ FULL STATUS\nresponse returned the ISID as \"0xleak\" followed by raw bytes that were not\npart of the parameter list. The snprintf() into\npr_reg_isid[PR_REG_ISID_LEN] caps the echoed ISID at 15 characters, so at\nmost 11 bytes past the buffer are leaked per command, but the PR OUT\ncommand is not rate limited.\n\nAny initiator that can send PR OUT to an iSCSI-exported LUN can trigger\neither variant, including a guest via vhost-scsi.\n\nRequire 8 bytes to remain after the \",i,0x\" separator, and a NUL inside the\nrest of the descriptor, before the ISID pointer is returned. REGISTER AND\nMOVE fails with TCM_INVALID_PARAMETER_LIST; on SPEC_I_PT no target port\nclaims the malformed TransportID, and the command fails the same way."
}
],
"id": "CVE-2026-99754",
"lastModified": "2026-11-20T06:18:13.530",
"metrics": {},
"published": "2026-11-20T06:18:13.530",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/29c5ce6465b5696fbdf8126fcd0a6946b005c8b7"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8a71f25a34439e99e094fabb619f787d15aaf9ae"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/cdf4b87a18cb6a0ee26865cb1b7b5660a491d302"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d1db24c32bbe7b998573392070c3a6bdd9f4066c"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.