From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-97519][MODERATE REGULAR] drm/xe: Fix null pointer dereference in devcoredump cleanup [ Upstream Date: Thu, 24 Sep 2026 14:32:44 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-97519 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 1 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: f5c3144f783f91d74b4fae84fb8bd7a4edf001f8 List-Id: CVE: CVE-2026-97519 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: drm/xe: Fix null pointer dereference in devcoredump cleanup [ Upstream Commit: f5c3144f783f91d74b4fae84fb8bd7a4edf001f8 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f5c3144f783f91d74b4fae84fb8bd7a4edf001f8 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97519 Analysis date: Thu, 24 Sep 2026 14:32:44 -0400 ActionableScore: 1 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-97519 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97519 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: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-97519 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-97519 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;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'A NULL pointer dereference can occur in the Intel xe devcoredump cleanup path when xe_devcoredump_snapshot_free processes a snapshot that was not fully populated and ss gt is NULL. The cleanup path can be reached without a prior successful capture and dereferencing ss gt while releasing matched GuC capture nodes can crash the kernel. A second issue concerns cancellation of deferred snapshot work that was not queued when no coredump was captured. For the CVSS the PR:L because a local process must be able to interact with the xe DRM device and induce the affected driver lifecycle, normally through access to an Intel GPU DRM render or primary node. The issue is not network reachable. Impact is local denial of service through a kernel crash. The available patch does not establish a use after free, out of bounds access, information disclosure, or write primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) YES NULLPTR SIMPLEFIX HARDWARE DEBUGFS DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1 * Raw paranoid score: 1 * Paranoid score: 1 * Final recommended bucket: **Ordinary Moderate**:: No floor or cap was applied. 2. Signal breakdown Positive signals: * +1 Reliable kernel crash or strong DoS. The patch directly fixes a NULL pointer dereference in xe_devcoredump_snapshot_free when ss->gt is NULL. Such a dereference can generate a kernel Oops or panic depending on system panic policy. Negative signals: * No negative score was applied. The Xe driver and Intel GPU requirement are not treated as rare hardware or a physical-only prerequisite. Important non-awarded signals: * No UAF or stale post-free object use is established. ss->gt is NULL, not shown to reference freed storage. * No concrete repeated release, put, free, or refcount mutation through a dangling reference exists. * No controlled reclaim, object replacement, arbitrary write, OOB access, information disclosure, or callback control is established. * No local unprivileged trigger point was awarded. The supplied patch does not establish that an ordinary render-node user can induce the incomplete devcoredump snapshot lifecycle. * No remote reachability point was awarded. This is a local DRM driver cleanup path. * No additional Availability point was awarded because the kernel crash is already counted by the single DoS signal. * No confidentiality or integrity point was awarded. A NULL pointer dereference alone does not establish disclosure or modification of protected state. 3. Reachability analysis The affected code is in the Intel Xe DRM devcoredump cleanup path. A trigger requires reaching a partially initialized devcoredump state where snapshot cleanup runs although ss->gt was never populated. A local process with access to a Xe DRM device may be able to submit GPU work, and GPU failures can lead to driver recovery or coredump handling. However, the supplied patch and visible context do not establish that an ordinary logged-in render-node user can reliably cause this specific incomplete capture and cleanup sequence. The complete privilege boundary is therefore unresolved. HostAdminRequired is UNKNOWN rather than YES because host administrative privilege is not proven. It is also not NO because below-host-admin reachability for the full trigger sequence is not proven. No namespace-scoped capability operation is shown, so NamespaceScopedPrivilege is UNKNOWN. This is not a network-reachable issue. No host setup, sysctl, boot option, or DRM master operation is shown as required by the available evidence. The Xe driver requires compatible Intel Xe-supported GPU hardware, but this alone is not sufficient evidence for a rare-hardware penalty. 4. Primitive and severity interpretation The exact primitive is an invalid-state NULL pointer dereference during devcoredump snapshot cleanup. The cleanup code dereferences ss->gt while ss->gt can be NULL if the snapshot was not fully populated. The second change avoids cancel_work_sync when deferred work was never queued because no coredump was captured. This is not an active structured-object UAF and not fixed stale storage. No object lifetime is shown to end before a later stale access. No first release that can free an object, surviving dangling reference, or second lifetime-mutating operation is present. The appropriate classification is CLASS_C because the demonstrated behavior is a crash-capable invalid dereference without an independently useful corruption primitive. The demonstrated consequence is local denial of service through a kernel Oops or panic. Privilege escalation, arbitrary kernel read or write, disclosure, integrity impact, and controlled reuse are speculative and unsupported. ImportantCandidate is NO because the patch supports only a constrained cleanup-path NULL dereference. AutoDowngradeAllowed is YES because no unresolved memory-corruption, ownership, authorization, or lifetime primitive remains after excluding the crash consequence. Manual review is still recommended to determine whether unprivileged Xe render-node users can reliably reach the affected devcoredump lifecycle in the evaluated product. 5. One-sentence report phrase A NULL pointer dereference in the Intel Xe devcoredump cleanup path can crash the kernel when an incompletely initialized snapshot is released, resulting in local denial of service. 6. Manual review recommendation MANUAL CHECK RECOMMENDED Confirm whether an ordinary user with Xe DRM render-node access can reliably induce an incomplete devcoredump snapshot and reach the cleanup path without requiring a privileged display or device-management operation. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: drm/xe: Fix null pointer dereference in devcoredump cleanup [ Upstream Commit: f5c3144f783f91d74b4fae84fb8bd7a4edf001f8 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f5c3144f783f91d74b4fae84fb8bd7a4edf001f8 Changed files: drivers/gpu/drm/xe/xe_devcoredump.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=f5c3144f783f91d74b4fae84fb8bd7a4edf001f8 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-97519 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97519 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:L/UI:N/S:U/C:N/I:N/A:H 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: 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: 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).