[CVE-2026-72362][MODERATE REGULAR] drm/xe/pt: Fix NULL pointer dereference in xe_pt_zap_ptes_entry() [ Upstream

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

CVE: CVE-2026-72362
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: drm/xe/pt: Fix NULL pointer dereference in xe_pt_zap_ptes_entry() [ Upstream
Commit: ff330ce16c846b70164ff0eb544c81219d4c5c08
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ff330ce16c846b70164ff0eb544c81219d4c5c08
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72362
Analysis date: Sun, 16 Aug 2026 04:21:34 -0400
ActionableScore: 3
ActionableScore lower bound: unknown
Actionable bucket: Borderline, manual review recommended
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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-72362	MODERATE	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:H';**CWE-476;CWE-754;CWE-703;BEST CVSS score: '5.5';DESCR 'A NULL pointer dereference in the Intel Xe DRM page table zap path can occur because xe_pt_zap_ptes_entry calls container_of on the child pointer before checking whether the page table walk supplied a NULL child. The page table walk framework may pass a NULL child for unpopulated entries, so a local process that can exercise Xe GPU VM or page table operations may crash the driver or trigger a kernel oops. For the CVSS the PR:L is used because reliable triggering requires local code execution with access to the DRM GPU interface, such as a render node or device node. The issue is not network reachable. Impact is denial of service through GPU driver crash or kernel availability loss. There is no clear UAF, OOB write, or arbitrary write primitive in this patch context, so confidentiality and integrity are not raised.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended (with actual score 3)	YES	NULLPTR SIMPLEFIX HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	YES	NO	checked

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

ActionableScore=3

1. ActionableScore
* Conservative score: 3
* Paranoid score: 3
* Final recommended bucket: **Borderline, manual review recommended**::

2. Signal breakdown
* Local unprivileged trigger: +1. A local process with access to the Intel Xe DRM GPU interface, such as a render node or device node, may be able to exercise GPU VM or page table zap operations.
* Reliable kernel crash / strong DoS: +1. The commit explicitly describes a NULL pointer dereference caused by calling container_of on a NULL child pointer, leading to a crash.
* Broad/default/common subsystem or broadly deployed exposure: +1. DRM render nodes and Intel GPU drivers are commonly exposed to local users on affected systems, though this is limited to systems using the Xe driver.
* Weak corruption only: +0. This is an invalid pointer / NULL dereference pattern, not a demonstrated UAF, OOB write, refcount takeover, callback overwrite, or attacker-controlled memory corruption primitive.
* No privilege escalation signal: +0. The patch does not show reclaim, stale object reuse, write-after-free, type confusion, or arbitrary write behavior.
* No remote reachability: +0. The affected path is local GPU driver control, not network packet processing.

3. Reachability analysis
A local user or local process with access to the Xe DRM device can potentially trigger the issue through GPU VM or page-table-management paths. This does not require CAP_SYS_ADMIN in the typical render-node model, but it does require access to the GPU device node, which may depend on udev permissions, group membership, desktop session policy, or container device passthrough. Containers only matter if the GPU device is delegated into the container. The path is not network reachable. The bug is hardware and driver dependent, affecting systems using the Intel Xe DRM driver rather than all Linux systems. Call-site confidence: medium, because the patch and commit describe the page-table walk behavior, but the full caller chain is not included.

4. Severity interpretation
This behaves like a local DoS issue rather than an Important-class vulnerability. The theoretical concern is that the bug occurs in GPU page-table handling, but the concrete primitive shown by the patch is only a NULL child pointer being passed to container_of before validation. There is no supported evidence of UAF, controlled overwrite, page ownership corruption, privilege escalation, or confidentiality/integrity impact. The issue should not be auto-treated as Important, but manual review is reasonable because DRM GPU interfaces are often reachable by unprivileged local users and crashes in GPU drivers can have operational impact.

5. One-sentence report phrase
A NULL pointer dereference in the Intel Xe DRM page-table zap path can allow a local process with GPU device access to crash the driver or kernel, with no evidence of privilege escalation or data disclosure.

6. Manual review recommendation
MANUAL CHECK RECOMMENDED.
The score is only borderline, but manual review is justified because the bug is in a local DRM/GPU interface that may be exposed to unprivileged users on affected systems.

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

Patch: drm/xe/pt: Fix NULL pointer dereference in xe_pt_zap_ptes_entry() [ Upstream
Commit: ff330ce16c846b70164ff0eb544c81219d4c5c08
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ff330ce16c846b70164ff0eb544c81219d4c5c08

Changed files:
  drivers/gpu/drm/xe/xe_pt.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=ff330ce16c846b70164ff0eb544c81219d4c5c08

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

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

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: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: 3

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