CVE-2026-72360
Linux drm/xe PF can crash when processing unexpected VF relay FAST_REQ/EVENT messages.
Is CVE-2026-72360 being exploited?
Not confirmed. CVE-2026-72360 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.17% probability of exploitation in the next 30 days.
How severe is CVE-2026-72360?
CVE-2026-72360 is rated High with a CVSS score of 8.4. 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-72360?
Yes. A fix has been recorded for CVE-2026-72360. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72360 affect?
CVE-2026-72360 affects Linux kernel (drm/xe PF driver), Systems using Intel Xe GPU VF/PF (SR-IOV), Hosts with GPU passthrough/virtualized GPUs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72360?
Apply vendor/kernel updates that include the drm/xe PF fix promptly
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted VF relay FAST_REQUEST/EVENT messages can trigger PF-side assert/kernel crash, enabling VM-to-host or local Denial of Service.
Patch when possible
- affected>= 98e62805921cebcd2fcac3692037ca2ebef63b4a and < 499be4b5d64209e9f18c9442f9fbeef7155ae900
- affected>= 98e62805921cebcd2fcac3692037ca2ebef63b4a and < adc7dda728ca3e340a413e3bbc10cf159e1866a4
- affected>= 98e62805921cebcd2fcac3692037ca2ebef63b4a and < a4208d8032abd7f591581994f31e23b80b8fe659
- affected>= 98e62805921cebcd2fcac3692037ca2ebef63b4a and < ed8b0d731892c68b41ecbd27c952af284816dec1
- affected6.11
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.