[CVE-2026-72360][MODERATE REGULAR] drm/xe/pf: Don't attempt to process FAST_REQ or EVENT relays [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-72360
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: drm/xe/pf: Don't attempt to process FAST_REQ or EVENT relays [ Upstream
Commit: 499be4b5d64209e9f18c9442f9fbeef7155ae900
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=499be4b5d64209e9f18c9442f9fbeef7155ae900
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72360
Analysis date: Sat, 15 Aug 2026 15:18:52 -0400
ActionableScore: 4
ActionableScore lower bound: 3
Actionable bucket: Borderline, manual review recommended / Actionable Moderate candidate
Manual review required: YES

Summary:
Unsupported FAST_REQUEST or EVENT relay messages from a VF could be incorrectly processed by the drm xe PF relay handler, breaking the VFPF ABI and potentially triggering a PF-side assert that disrupts the host GPU virtualization service.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72360 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72360

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE REGULAR
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-72360	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';*CWE-20;CWE-617;CWE-754;Other CVSS 'AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.7';DESCR 'The PF side of the drm xe SR IOV GuC relay path could treat unsupported FAST_REQUEST or EVENT relay actions as regular REQUEST messages. A VF controlled by an attacker could send such a message and break the expected VFPF ABI flow, which may trigger a PF side assertion and disrupt the host GPU service. For the CVSS the PR:L is used because the attacker needs control of a VF guest or a local process able to send VF relay traffic, not full host administrative privileges. The issue is not directly network reachable and is better modeled as an adjacent SR IOV boundary issue. Impact is denial of service against the PF or GPU virtualization service, with no concrete evidence of memory corruption, information disclosure, or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended / Actionable Moderate candidate (with actual score 4)  SKIP CVE-2026-72360 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 98e62805921cebcd2fcac3692037ca2ebef63b4a YES  NO NO unknown 	MAYBE	SIMPLEFIX HARDWARE  INCREASED_TO_MODERATE_FROM_LOW_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=4
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 4
* Final recommended bucket: **Borderline, manual review recommended / Actionable Moderate candidate**::

## 2. Signal breakdown

Conservative signals:

* Firmware-mediated or VF-mediated external influence: +1
  A VF can influence the PF relay path through the SR-IOV GuC relay channel. This is not ordinary Internet remote reachability, but it is an external virtualization boundary input.

* Reliable kernel crash / strong DoS concern: +1
  The commit says unsupported FAST_REQUEST or EVENT relay messages may trigger an assert on the PF side. This supports a PF-side availability concern, but not memory corruption.

* Cross-boundary isolation impact: +1
  The bug allows VF-originated protocol messages to affect PF-side handling. The demonstrated impact is DoS-like, not confidentiality or integrity compromise.

* Rare and configuration-dependent subsystem: -1
  The path requires drm/xe SR-IOV PF/VF GuC relay usage, which is narrower than default kernel networking or filesystem paths.

Paranoid additional signal:

* Availability impact realistic beyond local VF: +1
  If the PF-side assert disrupts the host GPU virtualization service, the impact may affect other VFs or GPU users on the host.

Not awarded:

* Generic memory corruption: +0
  The patch shows message type validation and rejection with EOPNOTSUPP. It does not show UAF, OOB access, double free, refcount misuse, type confusion, or arbitrary write.

* Privilege escalation plausible: +0
  No supported LPE primitive is visible.

* Confidentiality or integrity impact: +0
  No evidence of data disclosure, unauthorized write, or policy bypass beyond PF availability impact.

## 3. Reachability analysis

The likely attacker is a VF guest or a local actor able to send VF relay traffic to the PF. This should not be scored as network reachable because the affected interface is the SR-IOV VF/PF relay path, not an IP-exposed protocol. It also should not be treated as full host-root only, because a VF guest may be less privileged than the PF host and still influence the relay channel.

The path is configuration-dependent and requires Intel xe SR-IOV GuC relay PF services. It is not a broad default kernel path. Realistic exploitation depends on whether untrusted or tenant-controlled VFs are assigned on the affected host.

Call-site confidence: medium. The shown code includes the dispatch decision in relay_action_handler, but not the internals of xe_gt_sriov_pf_service_process_request or relay_assert behavior.

## 4. Severity interpretation

This behaves more like an Actionable Moderate candidate than an Important-class vulnerability. The reason for manual attention is the VF-to-PF boundary and possible PF-side assertion or host GPU service disruption. The patch does not support memory corruption, privilege escalation, information disclosure, or arbitrary code execution.

Theoretical worst case is host GPU virtualization DoS from a VF-controlled input. Realistic evidence supports protocol validation failure and possible assert-triggered DoS only.

## 5. One-sentence report phrase

Unsupported FAST_REQUEST or EVENT relay messages from a VF could be incorrectly processed by the drm xe PF relay handler, breaking the VFPF ABI and potentially triggering a PF-side assert that disrupts the host GPU virtualization service.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Manual review is required because the bug crosses a VF-to-PF virtualization boundary and may allow a guest-controlled VF to disrupt PF-side GPU service, even though the patch does not show memory corruption or privilege escalation.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: drm/xe/pf: Don't attempt to process FAST_REQ or EVENT relays [ Upstream
Commit: 499be4b5d64209e9f18c9442f9fbeef7155ae900
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=499be4b5d64209e9f18c9442f9fbeef7155ae900

Changed files:
  drivers/gpu/drm/xe/xe_guc_relay.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=499be4b5d64209e9f18c9442f9fbeef7155ae900

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72360 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72360

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 3
  Paranoid ActionableScore: 4

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).