CVE-2026-72083

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: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE

core_scsi3_emulate_pro_register_and_move() maps the PERSISTENT RESERVE OUT parameter list with transport_kmap_data_sg() and parses the destination TransportID with target_parse_pr_out_transport_id(). For an iSCSI TransportID (FORMAT CODE 01b), iscsi_parse_pr_out_transport_id() returns the ISID in iport_ptr as a raw pointer into that mapped buffer.

The function then unmaps the buffer with transport_kunmap_data_sg() before dereferencing iport_ptr in strcmp(), __core_scsi3_locate_pr_reg() and core_scsi3_alloc_registration(). When the parameter list spans more than one page (PARAMETER LIST LENGTH > 4096), transport_kmap_data_sg() uses vmap() and transport_kunmap_data_sg() does vunmap(), so the kernel virtual address backing iport_ptr is torn down and every subsequent dereference is a use-after-free read of the unmapped region.

Keep the parameter list mapped until iport_ptr is no longer needed: drop the early transport_kunmap_data_sg() and unmap once on the success path, right before returning. The error paths already unmap through the existing "if (buf) transport_kunmap_data_sg(cmd)" at the out: label, which now runs on every post-map error exit because buf is no longer cleared early. Only reads of the mapping happen while spinlocks are held; the map and unmap calls remain outside any lock. The sibling caller core_scsi3_decode_spec_i_port() already uses the buffer before unmapping it and is left unchanged.

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
52%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f8076cc73dfa6b10155978c160587e986b22169
generic

scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d56f5c868d92c9d504a34a3ea450bce481c7f63
generic

scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/59a2a5a37dc49a641ad6bc64aee34e5a61025ffd
generic

scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/05b3e37433cf2eaf8867f1c16528aa347bb212ab

Vendor Advisories for CVE-2026-72083(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 48× in last 7d / 48× 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:21 UTCGHSA enrichment
  2. 2026-08-21 05:07 UTCGHSA enrichment
  3. 2026-08-21 00:53 UTCEG score recompute
  4. 2026-08-21 00:53 UTCGHSA enrichment
  5. 2026-08-20 22:56 UTCEPSS rescore
  6. 2026-08-20 20:40 UTCGHSA enrichment
  7. 2026-08-20 16:26 UTCGHSA enrichment
  8. 2026-08-20 12:13 UTCGHSA enrichment
  9. 2026-08-20 07:59 UTCGHSA enrichment
  10. 2026-08-20 03:45 UTCGHSA enrichment
  11. 2026-08-19 23:31 UTCGHSA enrichment
  12. 2026-08-19 19:17 UTCEG score recompute
  13. 2026-08-19 19:17 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 14:54 UTCGHSA enrichment
  16. 2026-08-19 10:41 UTCGHSA enrichment
  17. 2026-08-19 06:20 UTCGHSA enrichment
  18. 2026-08-19 01:51 UTCGHSA enrichment
  19. 2026-08-18 21:37 UTCGHSA enrichment
  20. 2026-08-18 17:02 UTCEG score recompute
  21. 2026-08-18 17:02 UTCGHSA enrichment
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 12:04 UTCGHSA enrichment
  25. 2026-08-18 07:45 UTCGHSA enrichment
Show 23 more
  1. 2026-08-18 03:31 UTCGHSA enrichment
  2. 2026-08-17 23:18 UTCGHSA enrichment
  3. 2026-08-17 19:04 UTCGHSA enrichment
  4. 2026-08-17 14:49 UTCEG score recompute
  5. 2026-08-17 14:49 UTCGHSA enrichment
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 10:36 UTCEG score recompute
  8. 2026-08-17 10:35 UTCGHSA enrichment
  9. 2026-08-17 06:21 UTCEG score recompute
  10. 2026-08-17 06:21 UTCGHSA enrichment
  11. 2026-08-17 06:00 UTCEG score recompute 9.80
  12. 2026-08-17 06:00 UTCGHSA enrichment
  13. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  14. 2026-08-17 05:33 UTCEG score recompute
  15. 2026-08-17 05:33 UTCGHSA enrichment
  16. 2026-08-17 05:24 UTCMITRE cvelistV5
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 02:15 UTCEPSS rescore
  20. 2026-08-15 06:44 UTCGHSA enrichment
  21. 2026-08-15 06:23 UTCNVD update
  22. 2026-08-15 06:18 UTCEG score recompute
  23. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72083?
CVE-2026-72083 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE corescsi3emulateproregisterandmove() maps the PERSISTENT RESERVE OUT parameter list with transportkmapdata_sg() and parses the destination TransportID with…
When was CVE-2026-72083 disclosed?
CVE-2026-72083 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-72083 actively exploited?
CVE-2026-72083 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-72083?
CVE-2026-72083 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72083?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72083, 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-72083

Explore →

Is Your Infrastructure Affected by CVE-2026-72083?

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