# CVE-2026-72360: drm/xe/pf: Don't attempt to process FAST_REQ or EVENT relays

> A flaw in the Linux kernel's Xe GPU driver allows a virtual function to trigger a kernel assertion, causing a denial of service.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-72360, DEBIAN-CVE-2026-72360, GHSA-g429-9jp7-485v, UBUNTU-CVE-2026-72360

## What is CVE-2026-72360?

CVE-2026-72360 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/xe/pf: Don't attempt to process FAST_REQ or EVENT relays

Currently defined VF/PF relay actions use regular REQUEST messages
only and the PF shouldn't attempt to handle FAST_REQUEST nor EVENT
messages as this would result in breaking the VFPF ABI protocol
and also might trigger an assert on the PF side.

(cherry picked from commit 1714d360fc5ae2e0886a69e979095d9c7ff3568a)

## Which versions are affected by CVE-2026-72360?


## How do I fix CVE-2026-72360?

Apply the vendor's patch.

## Is CVE-2026-72360 being exploited?

There is no known exploitation of CVE-2026-72360 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72360 and fix it if it is affected.

What it is: CVE-2026-72360 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72360 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72360/ (Markdown: https://insights.sbomify.com/CVE-2026-72360/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72360
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72360
- OSV: https://osv.dev/vulnerability/CVE-2026-72360

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72360/
Summaries are generated and may contain mistakes; the official description above is the record.