[CVE-2026-74699][LOW] drm/xe: Fix memory leak in exec_queue_set_hang_replay_state() [ Upstream

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

CVE: CVE-2026-74699
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: drm/xe: Fix memory leak in exec_queue_set_hang_replay_state() [ Upstream
Commit: 410596743958fbddeb845ff3efe2645397d7c7e2
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=410596743958fbddeb845ff3efe2645397d7c7e2
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74699
Analysis date: Sat, 22 Aug 2026 13:56:58 -0400
ActionableScore: 2
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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: LOW
Manual review required: NO

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

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

CVE-2026-74699	LOW	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';*CWE-401;*CWE-772;**CWE-400;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'A memory leak in the drm xe exec queue ioctl path occurs because q replay_state can be overwritten by a new vmemdup_user allocation without releasing the previous allocation. A local process with access to the Xe DRM device can repeat the hang replay state operation on the same exec queue and consume kernel memory over time. For the CVSS the PR:L is used because reliable triggering requires local code execution and access to the DRM device interface, but it does not normally require full administrator privileges on systems that expose render nodes to users. The issue is not network reachable. Impact is denial of service through resource exhaustion, not information disclosure or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)  SKIP CVE-2026-74699 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES  NO NO unknown 	MAYBE	SIMPLEFIX LEAK HARDWARE  INCREASED_FROM_LOW_BASED_ON_HIGHCVSSSCORE DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

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

ActionableScore=2

1. ActionableScore
* Conservative score: 2
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**::

2. Signal breakdown
* Local unprivileged trigger: +1. A local process with access to the Xe DRM device node can likely reach the ioctl path. This is PR:L, not PR:H, because DRM render nodes are commonly exposed to non-root graphical users.
* Availability impact realistic: +1. Repeated overwrites of q->replay_state can leak vmemdup_user allocations and may cause memory pressure or resource exhaustion over time.
* No generic memory corruption: +0. The patch shows a lost allocation pointer, not UAF, double free, OOB write, type confusion, refcount takeover, or attacker-controlled overwrite.
* No privilege escalation plausible: +0. The described primitive is resource leakage only.
* No remote/network trigger: +0. This is a local DRM ioctl path.
* No high-control API bonus: +0. RDMA/GPU/device object APIs are not enough by themselves. The patch does not show attacker control over object lifetime, callbacks, refcounts, DMA mappings, or page ownership beyond leaking an allocation.

3. Reachability analysis
A local user or process with access to the Xe DRM device interface can potentially trigger the bug by repeatedly setting hang replay state on the same exec queue. Containers may matter only if the DRM device node is passed through, in which case this remains PR:L inside that delegated environment. The path is not network reachable. It requires Intel Xe DRM support and an accessible device node, so exposure is hardware and deployment dependent, but not an unusual privileged-only kernel path on systems where render nodes are available to users.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like resource exhaustion issue, not an Important-class kernel vulnerability. The theoretical worst case is local denial of service through accumulated kernel memory leakage. There is no evidence in the patch of memory corruption, stale object reuse, write-after-free, arbitrary write, page-cache corruption, or a practical LPE primitive.

5. One-sentence report phrase
A local memory leak in the drm xe exec queue ioctl path allows repeated q replay_state overwrites to leak vmemdup_user allocations, potentially causing denial of service through resource exhaustion but not indicating privilege escalation or remote reachability.

6. Manual review recommendation
NO MANUAL CHECK NEEDED
This is a local resource leak without evidence of memory corruption, privilege escalation, network exposure, or security-boundary bypass, so it can be handled as a low-priority Moderate resource-exhaustion issue.

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

Patch: drm/xe: Fix memory leak in exec_queue_set_hang_replay_state() [ Upstream
Commit: 410596743958fbddeb845ff3efe2645397d7c7e2
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=410596743958fbddeb845ff3efe2645397d7c7e2

Changed files:
  drivers/gpu/drm/xe/xe_exec_queue.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=410596743958fbddeb845ff3efe2645397d7c7e2

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

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

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:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.5

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: unknown
  Paranoid ActionableScore: 2

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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).