CVE-2026-72084

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (7)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

scsi: target: Bound PR-OUT TransportID parsing to the received buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d04a179085c262c9ed577d0a4cbc6482ff1fd9a3
generic

scsi: target: Bound PR-OUT TransportID parsing to the received buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9298078a8f7d8181a04614a34ab655ccdf038204
generic

scsi: target: Bound PR-OUT TransportID parsing to the received buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/842248047ef28dbf3b3f7f49a0ec315054d4dab8
generic

scsi: target: Bound PR-OUT TransportID parsing to the received buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ca5de8782e67573a61a6736b6dc0ffe58dcdf59
generic

scsi: target: Bound PR-OUT TransportID parsing to the received buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/555a89846ed888d7401b3f7200934c0fbedcbb46
generic

scsi: target: Bound PR-OUT TransportID parsing to the received buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03fbc7de8d5e85fc8420e57e8304c855efd453ab
generic

scsi: target: Bound PR-OUT TransportID parsing to the received buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/004ccd2d3b4ac36a300e05e01df152e5c02a5a82

Vendor Advisories for CVE-2026-72084(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 51× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 09:03 UTCGHSA enrichment
  2. 2026-08-21 05:18 UTCGHSA enrichment
  3. 2026-08-21 01:32 UTCEG score recompute
  4. 2026-08-21 01:32 UTCGHSA enrichment
  5. 2026-08-20 22:56 UTCEPSS rescore
  6. 2026-08-20 21:47 UTCGHSA enrichment
  7. 2026-08-20 18:01 UTCGHSA enrichment
  8. 2026-08-20 14:16 UTCGHSA enrichment
  9. 2026-08-20 10:23 UTCGHSA enrichment
  10. 2026-08-20 06:38 UTCGHSA enrichment
  11. 2026-08-20 02:53 UTCGHSA enrichment
  12. 2026-08-19 23:08 UTCGHSA enrichment
  13. 2026-08-19 19:23 UTCEG score recompute
  14. 2026-08-19 19:23 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-19 15:38 UTCGHSA enrichment
  17. 2026-08-19 11:53 UTCGHSA enrichment
  18. 2026-08-19 08:07 UTCGHSA enrichment
  19. 2026-08-19 04:22 UTCGHSA enrichment
  20. 2026-08-19 00:34 UTCGHSA enrichment
  21. 2026-08-18 20:47 UTCGHSA enrichment
  22. 2026-08-18 17:02 UTCEG score recompute
  23. 2026-08-18 17:02 UTCGHSA enrichment
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 13:49 UTCEPSS rescore
Show 26 more
  1. 2026-08-18 12:41 UTCGHSA enrichment
  2. 2026-08-18 08:45 UTCGHSA enrichment
  3. 2026-08-18 05:00 UTCGHSA enrichment
  4. 2026-08-18 01:14 UTCGHSA enrichment
  5. 2026-08-17 21:26 UTCGHSA enrichment
  6. 2026-08-17 17:40 UTCGHSA enrichment
  7. 2026-08-17 13:51 UTCEG score recompute
  8. 2026-08-17 13:51 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 10:06 UTCEG score recompute
  11. 2026-08-17 10:06 UTCGHSA enrichment
  12. 2026-08-17 06:21 UTCEG score recompute
  13. 2026-08-17 06:21 UTCGHSA enrichment
  14. 2026-08-17 06:00 UTCEG score recompute 9.80
  15. 2026-08-17 06:00 UTCGHSA enrichment
  16. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  17. 2026-08-17 05:33 UTCEG score recompute
  18. 2026-08-17 05:33 UTCGHSA enrichment
  19. 2026-08-17 05:25 UTCMITRE cvelistV5
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:15 UTCEPSS rescore
  23. 2026-08-15 06:44 UTCGHSA enrichment
  24. 2026-08-15 06:23 UTCNVD update
  25. 2026-08-15 06:18 UTCEG score recompute
  26. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72084?
CVE-2026-72084 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: target: Bound PR-OUT TransportID parsing to the received buffer corescsi3decodespeciport() and corescsi3emulateregisterandmove() hand the raw PERSISTENT RESERVE OUT parameter buffer to targetparseprouttransport_id() without…
When was CVE-2026-72084 disclosed?
CVE-2026-72084 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72084 actively exploited?
CVE-2026-72084 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.6% of all scored CVEs.
What is the CVSS score of CVE-2026-72084?
CVE-2026-72084 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72084?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72084, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72084

Explore →

Is Your Infrastructure Affected by CVE-2026-72084?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.