scsi: target: Bound PR-OUT TransportID parsing to the received buffer
In the Linux kernel, the following vulnerability has been resolved: scsi: target: Bound PR-OUT TransportID parsing to the received buffer core_scsi3_decode_spec_i_port() and core_scsi3_emulate_register_and_move() hand the raw PERSISTENT RESERVE OUT parameter buffer to target_parse_pr_out_transport_id() without telling it how many bytes are valid. For an iSCSI TransportID (FORMAT CODE 01b), iscsi_parse_pr_out_transport_id() locates the ",i,0x" ISID separator with an unbounded strstr() (and on the error path prints the name with a further unbounded "%s"). An initiator can submit a TransportID whose iSCSI name contains neither a ",i,0x" substring nor a NUL terminator, filling the parameter list to its end, so the scan runs off the end of the buffer. When the parameter list spans more than one page the buffer is a multi-page vmap (transport_kmap_data_sg()), so the over-read walks into the trailing vmalloc guard page and oopses (KASAN: vmalloc-out-of-bounds in strstr). It is reachable by any fabric that delivers a PR OUT to a device exported through an iSCSI TPG, including a guest via vhost-scsi. Pass the number of received bytes down to the parser and validate the iSCSI TransportID's own self-described length (ADDITIONAL LENGTH + 4) once, up front: reject it if it is below the spc4r17 minimum or larger than the received buffer, then bound the separator search, the ISID walk and the name copy by that length. This is the length check the callers already perform after the parse (core_scsi3_decode_spec_i_port() compares tid_len against tpdl, core_scsi3_emulate_register_and_move() validates it against data_length), moved ahead of the scan. Also drop the unbounded "%s" of the unterminated name. Add per-format explicit name-length checks before copying into i_str, rather than silently truncating with min_t: for FORMAT CODE 00b reject if the descriptor body (tid_len - 4 bytes) cannot fit in i_str[TRANSPORT_IQN_LEN]; for FORMAT CODE 01b reject if the name portion (from &buf[4] up to the separator) cannot fit. Both checks make the bounds intent explicit at each format branch. While here, also reject a FORMAT CODE 01b TransportID whose ",i,0x" separator sits at the very end of the descriptor: that leaves an empty ISID and points the returned port nexus pointer at buf + tid_len, one past the descriptor, which the registration code (__core_scsi3_locate_pr_reg(), __core_scsi3_alloc_registration()) then dereferences as the ISID string -- the same over-read of the parameter buffer for a malformed descriptor.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Aug 15, 2026
- Updated
- Aug 23, 2026
- EPSS
- 0.8% · 53th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.38affected
- c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 and later · before 88c67c3de914e19172e1d878a7625c5b06c20ec5affected · git
- c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 and later · before 842248047ef28dbf3b3f7f49a0ec315054d4dab8affected · git
- c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 and later · before 03fbc7de8d5e85fc8420e57e8304c855efd453abaffected · git
- c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 and later · before 6ca5de8782e67573a61a6736b6dc0ffe58dcdf59affected · git
- c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 and later · before 9298078a8f7d8181a04614a34ab655ccdf038204affected · git
- c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 and later · before 004ccd2d3b4ac36a300e05e01df152e5c02a5a82affected · git
- c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 and later · before 555a89846ed888d7401b3f7200934c0fbedcbb46affected · git
- c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 and later · before d04a179085c262c9ed577d0a4cbc6482ff1fd9a3affected · git
- before 2.6.38not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 004ccd2d3b4ac36a300e05e01df152e5c02a5a82 | Vendor (CNA) |
| Linux Linux | 03fbc7de8d5e85fc8420e57e8304c855efd453ab | Vendor (CNA) |
| Linux Linux | 555a89846ed888d7401b3f7200934c0fbedcbb46 | Vendor (CNA) |
| Linux Linux | 6ca5de8782e67573a61a6736b6dc0ffe58dcdf59 | Vendor (CNA) |
| Linux Linux | 842248047ef28dbf3b3f7f49a0ec315054d4dab8 | Vendor (CNA) |
| Linux Linux | 88c67c3de914e19172e1d878a7625c5b06c20ec5 | Vendor (CNA) |
| Linux Linux | 9298078a8f7d8181a04614a34ab655ccdf038204 | Vendor (CNA) |
| Linux Linux | d04a179085c262c9ed577d0a4cbc6482ff1fd9a3 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/004ccd2d3b4ac36a300e05e01df152e5c02a5a82
- git.kernel.org/stable/c/03fbc7de8d5e85fc8420e57e8304c855efd453ab
- git.kernel.org/stable/c/555a89846ed888d7401b3f7200934c0fbedcbb46
- git.kernel.org/stable/c/6ca5de8782e67573a61a6736b6dc0ffe58dcdf59
- git.kernel.org/stable/c/842248047ef28dbf3b3f7f49a0ec315054d4dab8
- git.kernel.org/stable/c/88c67c3de914e19172e1d878a7625c5b06c20ec5
- git.kernel.org/stable/c/9298078a8f7d8181a04614a34ab655ccdf038204
- git.kernel.org/stable/c/d04a179085c262c9ed577d0a4cbc6482ff1fd9a3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.