[CVE-2026-68305][LOW] drm/xe/vf: Add drm_dev guards when detaching CCS read/write buffers [ Upstream

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

CVE: CVE-2026-68305
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: drm/xe/vf: Add drm_dev guards when detaching CCS read/write buffers [ Upstream
Commit: 523ed2831ee55b2a1edabdea96781651f9df9685
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=523ed2831ee55b2a1edabdea96781651f9df9685
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68305
Analysis date: Mon, 10 Aug 2026 14:27:58 -0400
ActionableScore: 2
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A local DRM xe SR-IOV VF teardown bug can cause a NULL pointer dereference when CCS buffers are detached after device unbind, leading to a kernel crash, but the issue requires a narrow teardown window and shows no supported confidentiality, integrity, or privilege escalation primitive.

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

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

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-68305	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;*CWE-664;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'drm xe VF CCS BO teardown can hit a NULL pointer dereference when BO destruction runs after the GPU device has been unbound while the DRM object is still valid. The failure path reaches xe_sriov_vf_ccs_rw_update_bb_addr through xe_migrate_ccs_rw_copy_clear while detaching CCS read and write buffers, causing a kernel Oops and denial of service. For the CVSS the PR:L is used in the paranoid score because an untrusted local user may be able to create and destroy DRM buffer objects through a render node while device teardown is triggered by admin action or platform events. The base score keeps PR:H because reliable triggering normally requires control over device unbind or equivalent driver teardown. The issue is not network reachable. Impact is denial of service only because the patch context shows a NULL dereference on unavailable device resources, not a UAF, OOB access, information leak, or write primitive.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)  SKIP CVE-2026-68305 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 864690cf4dd62482b6dd049d82c509886c904303 YES  NO NO unknown 	MAYBE	READ DANGER NULLPTR INIT UAF HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

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

ActionableScore=2
ActionableScoreLower=0

## 1. ActionableScore

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

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1. The commit includes a concrete NULL pointer dereference and Oops in `xe_sriov_vf_ccs_rw_update_bb_addr()`.
* Requires admin/root/CAP_* in typical deployments: -2. Reliable triggering normally requires device unbind or equivalent DRM driver teardown control.
* Rare AND difficult-to-reach subsystem/configuration: -1. This is specific to Intel `drm/xe` SR-IOV VF CCS buffer handling, not a broad default kernel path.
* Hard or special timing required: -1. The BO must be destroyed after device unbind while the DRM structure remains valid.

Paranoid signals:

* Local unprivileged trigger: +1. A local user may be able to create and destroy DRM BOs through a render node, while unbind/reset is caused by admin action or platform events.
* Reliable kernel crash / strong DoS: +1. The failure mode is a demonstrated kernel NULL dereference.
* Hard or special timing required: -1. The teardown/unbind timing window is still required.
* Rare AND difficult-to-reach subsystem/configuration: -1. The affected path is hardware and SR-IOV VF specific.

Not awarded:

* No generic memory corruption. The patch shows NULL dereference on unavailable device resources, not UAF, double free, OOB write, type confusion, or refcount takeover.
* No privilege escalation plausible. There is no reclaim, callback control, write primitive, or attacker-controlled object replacement.
* No confidentiality or integrity impact. The demonstrated consequence is crash only.
* No network reachability. This is a local DRM/device teardown path.

## 3. Reachability analysis

The conservative trigger requires administrative control over device unbind or similar driver teardown. A normal unprivileged user is unlikely to reliably cause the full condition alone.

The paranoid interpretation considers a mixed scenario where an unprivileged local user creates DRM buffer objects through a render node and later exits or destroys mappings while device teardown happens concurrently. That still depends on external unbind/reset timing, so it remains weak as an attacker-controlled path.

Namespaces and containers do not obviously lower the requirement unless the container is given access to the DRM render node and the host device lifecycle can be influenced. The path is not remotely reachable and is limited to systems using the Intel `xe` driver with SR-IOV VF CCS support.

Call-site confidence: high. The provided stack trace and patch show the relevant call chain from BO destruction to CCS detach and the guarded device-resource access.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like local DoS issue, not an Important-class vulnerability. The realistic impact is a kernel crash during a narrow device teardown window. Theoretical memory-corruption escalation is not supported by the patch because the failure is a NULL pointer dereference, and the fix only guards device access with `drm_dev_enter()` / `drm_dev_exit()`.

## 5. One-sentence report phrase

A local DRM xe SR-IOV VF teardown bug can cause a NULL pointer dereference when CCS buffers are detached after device unbind, leading to a kernel crash, but the issue requires a narrow teardown window and shows no supported confidentiality, integrity, or privilege escalation primitive.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be handled as non-actionable Moderate or Low-like unless the product specifically exposes Intel `xe` SR-IOV VF CCS functionality to untrusted local users and has a realistic way for them to influence device teardown.

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

Patch: drm/xe/vf: Add drm_dev guards when detaching CCS read/write buffers [ Upstream
Commit: 523ed2831ee55b2a1edabdea96781651f9df9685
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=523ed2831ee55b2a1edabdea96781651f9df9685

Changed files:
  drivers/gpu/drm/xe/xe_migrate.c
  drivers/gpu/drm/xe/xe_migrate.h
  drivers/gpu/drm/xe/xe_sriov_vf_ccs.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=523ed2831ee55b2a1edabdea96781651f9df9685

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

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

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