Skip to content
Systems

CVE-2026-72085

9.3
Critical
EPSS 0.18%Patch availableAug 17, 2026

Xen scsiback kernel bug lets a pvSCSI guest cause LUN DoS and may panic the host.

common questions

Is CVE-2026-72085 being exploited?

Not confirmed. CVE-2026-72085 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.18% probability of exploitation in the next 30 days.

How severe is CVE-2026-72085?

CVE-2026-72085 is rated Critical with a CVSS score of 9.3. 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-72085?

Yes. A fix has been recorded for CVE-2026-72085. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72085 affect?

CVE-2026-72085 affects Linux kernel (Xen scsiback / vscsibk), Xen hosts running scsiback, pvSCSI guests on affected hosts. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72085?

Apply Linux kernel/Xen scsiback patches immediately; update hosts and restrict untrusted guests.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (Xen scsiback / vscsibk)Xen hosts running scsibackpvSCSI guests on affected hosts
impact

A paravirtualized (pvSCSI) guest can leak command tags to stop a LUN (DoS) and may trigger host panic; underflow can lead to use-after-free conditions.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 2dbcdf33dbf61f44b29adb52338282c3d7840d0e and < 9c0f6894982b1f13bda220707497b25ac9c95bdb
  • affected>= 2dbcdf33dbf61f44b29adb52338282c3d7840d0e and < a13b789497a7fdd27d4d63f5c69d23db706ef0fe
  • affected>= 2dbcdf33dbf61f44b29adb52338282c3d7840d0e and < fa588f28401102652068c4cc75e135507f4b5106
  • affected>= 2dbcdf33dbf61f44b29adb52338282c3d7840d0e and < fcd64d4d97af5d9736f31040f8ed8cd4c17e4c45
  • affected>= 2dbcdf33dbf61f44b29adb52338282c3d7840d0e and < f1516c56ac540da1769f264c3cfefe4499548a5d
  • affected>= 2dbcdf33dbf61f44b29adb52338282c3d7840d0e and < 1e97c404e44991fb087c38ccd7414f2d326f9b74
  • affected>= 2dbcdf33dbf61f44b29adb52338282c3d7840d0e and < ca978f8a93d4d36841839bf2847d29b88c2591d6
  • affected4.6
vendor says fixed in< 4.6, >= 5.15.212 and <= 5.15.*, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free