[CVE-2026-80606][LOW] drm/xe/userptr: Hold notifier_lock for write on inject test path [ Upstream

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

CVE: CVE-2026-80606
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: drm/xe/userptr: Hold notifier_lock for write on inject test path [ Upstream
Commit: f9a9abd7bbdab3dfe1b1155e1457dc02b5e14ea5
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f9a9abd7bbdab3dfe1b1155e1457dc02b5e14ea5
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80606
Analysis date: Fri, 28 Aug 2026 03:54:36 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A lock mode mismatch in the DRM Xe userptr invalidation injection path can trigger a lockdep WARN through the local VM bind ioctl when CONFIG_DRM_XE_USERPTR_INVAL_INJECT is enabled, with practical impact limited to warning or local DoS on panic-on-warn test kernels.

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

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

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-80606	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	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:L';CWE-667;CWE-703;CWE-754;BEST CVSS score: '3.3';DESCR 'Low risk. This is a test injection configuration issue rather than a production memory corruption bug. Manual review can be skipped unless the affected build enables CONFIG_DRM_XE_USERPTR_INVAL_INJECT in production or treats WARN as panic.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	WRITE OOB HARDWARE TEST  DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_GUESSCVSS	YES	NO	checked

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

ActionableScore=1
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

Conservative signals:

* Local trigger surface: +1. The call path reaches `xe_vm_bind_ioctl`, so a local process with access to the Xe DRM device node could potentially trigger it.
* Legacy / non-default execution mode: -1. The issue requires `CONFIG_DRM_XE_USERPTR_INVAL_INJECT=y`, which is explicitly a test injection configuration. Production builds with this option disabled keep the existing behavior.
* WARN-only behavior: +0. The described failure is a lockdep assertion warning, not a demonstrated Oops, UAF, OOB access, double free, arbitrary write, or privilege boundary bypass.

Paranoid additional signal:

* Possible local DoS on panic-on-warn systems: +1. If the affected test kernel is configured to panic on WARN, the assertion can become a local availability issue.

Not awarded:

* No generic memory corruption. The patch fixes lock mode correctness, not a stale pointer, overwrite, UAF, object confusion, or refcount bug.
* No privilege escalation plausible. The patch context does not show attacker-controlled reclaim, callback control, write-after-free, type confusion, or arbitrary write.
* No confidentiality or integrity impact. There is no supported leak or unauthorized modification primitive.
* No network reachability. The trigger is through a local DRM ioctl path, not packet processing or a remote protocol.

## 3. Reachability analysis

A local process with access to the Xe DRM render or device node may reach the relevant VM bind path. However, the problematic behavior is gated by `CONFIG_DRM_XE_USERPTR_INVAL_INJECT=y`, which is a fault-injection or test option and should not normally be enabled in production kernels. Namespaces or containers matter only if the Xe DRM device node is passed through to the container. Even then, the affected kernel must be built with the injection option enabled.

Call-site confidence: high. The provided trace and diff show the path through `xe_vm_bind_ioctl`, `xe_pt_svm_userptr_pre_commit`, `vma_check_userptr`, and the injected invalidation path.

## 4. Severity interpretation

This behaves like a Low or ordinary Moderate issue, not an Important-class vulnerability. The realistic impact is a lockdep WARN in a non-default test configuration. A paranoid availability concern exists only for systems that both enable the injection Kconfig and treat WARN as panic. There is no evidence of practical memory corruption, privilege escalation, information disclosure, or cross-boundary policy bypass.

## 5. One-sentence report phrase

A lock mode mismatch in the DRM Xe userptr invalidation injection path can trigger a lockdep WARN through the local VM bind ioctl when CONFIG_DRM_XE_USERPTR_INVAL_INJECT is enabled, with practical impact limited to warning or local DoS on panic-on-warn test kernels.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: this is a test-injection-only lock assertion issue with no supported memory corruption or privilege escalation primitive. Manual review is only justified if the evaluated product ships production kernels with `CONFIG_DRM_XE_USERPTR_INVAL_INJECT=y` or enables panic-on-warn in affected deployments.

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

Patch: drm/xe/userptr: Hold notifier_lock for write on inject test path [ Upstream
Commit: f9a9abd7bbdab3dfe1b1155e1457dc02b5e14ea5
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f9a9abd7bbdab3dfe1b1155e1457dc02b5e14ea5

Changed files:
  drivers/gpu/drm/drm_gpusvm.c
  drivers/gpu/drm/xe/xe_pt.c
  drivers/gpu/drm/xe/xe_svm.h

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=f9a9abd7bbdab3dfe1b1155e1457dc02b5e14ea5

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

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

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

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: 0
  Paranoid ActionableScore: 1

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