Linux kernel vulnerability in widely deployed scsi/iSCSI target code with high CVSS that can disrupt storage servers and host OSes.
CVE-2026-72083
Linux kernel iSCSI use-after-free allowing kernel memory read or crash
Is CVE-2026-72083 being exploited?
Not confirmed. CVE-2026-72083 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.72% probability of exploitation in the next 30 days.
How severe is CVE-2026-72083?
CVE-2026-72083 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72083?
Yes. A fix has been recorded for CVE-2026-72083. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72083 affect?
CVE-2026-72083 affects Linux kernel (scsi/target subsystem), iSCSI target servers and storage gateways. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72083?
Apply vendor kernel security updates and restrict/isolated iSCSI access immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote iSCSI initiator can trigger a use-after-free read, causing kernel memory disclosure, system crash (DoS), and potentially privilege escalation.
Immediate action required
- affected>= 4949314c7283ea4f9ade182ca599583b89f7edd6 and < 7d56f5c868d92c9d504a34a3ea450bce481c7f63
- affected>= 4949314c7283ea4f9ade182ca599583b89f7edd6 and < 59a2a5a37dc49a641ad6bc64aee34e5a61025ffd
- affected>= 4949314c7283ea4f9ade182ca599583b89f7edd6 and < 9f8076cc73dfa6b10155978c160587e986b22169
- affected>= 4949314c7283ea4f9ade182ca599583b89f7edd6 and < a040004846f1fbe687f6ec76d9ccc27b4ead42e4
- affected>= 4949314c7283ea4f9ade182ca599583b89f7edd6 and < 05b3e37433cf2eaf8867f1c16528aa347bb212ab
- affected>= 4949314c7283ea4f9ade182ca599583b89f7edd6 and < cb7bdae7fba404852ade34b0c1445fbaf3e54fbb
- affected>= 4949314c7283ea4f9ade182ca599583b89f7edd6 and < ef2ee18fec92088c7d8877baf7674e89389ccd66
- affected>= 4949314c7283ea4f9ade182ca599583b89f7edd6 and < fda6a1f3c3d7047b5ce5654487649c2daa738bfc
- affectedd2227f84ba0e97906153ac83db13213fb2e3938d
- affected>= 3.2.9 and < 3.3
- affected3.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.