CVE-2026-72083: scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.72% (FIRST EPSS); higher than 54.6% of all records.
- 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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 05b3e37433cf2eaf8867f1c16528aa347bb212ab, 3.3, 59a2a5a37dc49a641ad6bc64aee34e5a61025ffd.
Low priority for now. Upgrade to Linux Linux 05b3e37433cf2eaf8867f1c16528aa347bb212ab, 3.3, 59a2a5a37dc49a641ad6bc64aee34e5a61025ffd or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.7% · 54th percentile
- CWE
- CWE-416
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
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
- d2227f84ba0e97906153ac83db13213fb2e3938d, 3.3affected
- 4949314c7283ea4f9ade182ca599583b89f7edd6 and later · before 7d56f5c868d92c9d504a34a3ea450bce481c7f63affected · git
- 4949314c7283ea4f9ade182ca599583b89f7edd6 and later · before 59a2a5a37dc49a641ad6bc64aee34e5a61025ffdaffected · git
- 4949314c7283ea4f9ade182ca599583b89f7edd6 and later · before 9f8076cc73dfa6b10155978c160587e986b22169affected · git
- 4949314c7283ea4f9ade182ca599583b89f7edd6 and later · before a040004846f1fbe687f6ec76d9ccc27b4ead42e4affected · git
- 4949314c7283ea4f9ade182ca599583b89f7edd6 and later · before 05b3e37433cf2eaf8867f1c16528aa347bb212abaffected · git
- 4949314c7283ea4f9ade182ca599583b89f7edd6 and later · before cb7bdae7fba404852ade34b0c1445fbaf3e54fbbaffected · git
- 4949314c7283ea4f9ade182ca599583b89f7edd6 and later · before ef2ee18fec92088c7d8877baf7674e89389ccd66affected · git
- 4949314c7283ea4f9ade182ca599583b89f7edd6 and later · before fda6a1f3c3d7047b5ce5654487649c2daa738bfcaffected · git
- 3.2.9 and later · before 3.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.69.1.el10_2 | 6.12.0-211.69.1.el10_2 |
+96
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
Published before and after this one in the same product
- ← EarlierCVE-2026-72073Aug 15, 2026 · mmc: vub300: fix use-after-free on probe failure0Monitor
- ← EarlierCVE-2026-72080Aug 15, 2026 · fs/resctrl: Fix use-after-free during unmount31Monitor
- Later →CVE-2026-72084Aug 15, 2026 · scsi: target: Bound PR-OUT TransportID parsing to the received buffer39Monitor
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 | 05b3e37433cf2eaf8867f1c16528aa347bb212ab | Vendor (CNA) |
| Linux Linux | 3.3 | Vendor (CNA) |
| Linux Linux | 59a2a5a37dc49a641ad6bc64aee34e5a61025ffd | Vendor (CNA) |
| Linux Linux | 7d56f5c868d92c9d504a34a3ea450bce481c7f63 | Vendor (CNA) |
| Linux Linux | 9f8076cc73dfa6b10155978c160587e986b22169 | Vendor (CNA) |
| Linux Linux | a040004846f1fbe687f6ec76d9ccc27b4ead42e4 | Vendor (CNA) |
| Linux Linux | cb7bdae7fba404852ade34b0c1445fbaf3e54fbb | Vendor (CNA) |
| Linux Linux | ef2ee18fec92088c7d8877baf7674e89389ccd66 | Vendor (CNA) |
| Linux Linux | fda6a1f3c3d7047b5ce5654487649c2daa738bfc | Vendor (CNA) |
| almalinux:kernel | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.69.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.69.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.69.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.69.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.69.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.69.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.69.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.69.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-211.69.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
+12
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).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-720690 days apartlocking/rt: Fix the incorrect RCU protection in rt_spin_unlock()39Monitor
- CVE-2026-681175 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()39Monitor
- CVE-2026-681275 days apartila: reload IPv6 header after pskb_may_pull in checksum adjust39Monitor
- CVE-2026-681565 days apartlibceph: refresh auth->authorizer_buf{,_len} after authorizer update39Monitor
- CVE-2026-683815 days apartksmbd: pin conn during async oplock break notification39Monitor
- CVE-2026-684265 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment39Monitor
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
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)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/59a2a5a37dc49a641ad6bc64aee34e5a61025ffd
- git.kernel.org/stable/c/7d56f5c868d92c9d504a34a3ea450bce481c7f63
- git.kernel.org/stable/c/9f8076cc73dfa6b10155978c160587e986b22169
- git.kernel.org/stable/c/a040004846f1fbe687f6ec76d9ccc27b4ead42e4
- git.kernel.org/stable/c/cb7bdae7fba404852ade34b0c1445fbaf3e54fbb
- git.kernel.org/stable/c/ef2ee18fec92088c7d8877baf7674e89389ccd66
- git.kernel.org/stable/c/fda6a1f3c3d7047b5ce5654487649c2daa738bfc
Vendor advisories and official records. Exploit/PoC links are deliberately left out.