From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-93248][LOW] drm/xe: don't WARN on kernel job timeout when device already wedged [ Upstream Date: Thu, 24 Sep 2026 17:59:12 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-93248 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 0 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 24d81b72992006f9c390f1fc85c7f991e6d06fd6 List-Id: CVE: CVE-2026-93248 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: drm/xe: don't WARN on kernel job timeout when device already wedged [ Upstream Commit: 24d81b72992006f9c390f1fc85c7f991e6d06fd6 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=24d81b72992006f9c390f1fc85c7f991e6d06fd6 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93248 Analysis date: Thu, 24 Sep 2026 17:59:12 -0400 ActionableScore: 0 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-93248 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93248 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-93248 LOW https://www.kernelcve.org/list/?q=CVE-2026-93248 CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N';CWE-703;CWE-617;BEST CVSS score: '0';DESCR 'A drm xe kernel job timeout during teardown of an already wedged GPU can incorrectly be treated as unexpected when the affected execution queue was killed. This produces a WARN and taints the kernel even though the device is already wedged and the GuC CT path cannot complete the job. For the CVSS the PR:H reflects that reproducing the full wedge and driver rebind teardown scenario normally requires administrative test or driver management capabilities. The issue is local and not network reachable. Impact is limited to an erroneous diagnostic warning and kernel taint. No memory corruption, privilege escalation, confidentiality impact, integrity impact, or additional denial of service primitive is indicated by the patch.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0) YES WARNONLY SIMPLEFIX HARDWARE YES NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=0 PrimitiveClass=NONE RealUAF=NO HostAdminRequired=YES NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 0 * Conservative score: 0 * Raw paranoid score: 0 * Paranoid score: 0 * Final recommended bucket: **Ordinary Moderate**:: No floor or cap was applied. The patch establishes only an expected-timeout WARN handling defect, not a security primitive. 2. Signal breakdown * +0 No corruption primitive. The change only preserves the pre-existing device wedged state for a killed execution queue. * +0 No reliable new DoS. The GPU is already wedged before the affected timeout path executes. The patch does not prevent or create the initial GPU wedge. * +0 WARN and kernel taint. A WARN alone is not a separate security or availability impact. * +0 No UAF, stale pointer, refcount mutation, double release, OOB access, arbitrary write, information disclosure, authorization bypass, or ownership violation is established. * +0 Remote reachability is not established. The path executes in local DRM Xe driver timeout and teardown processing. * +0 Structured stale-object leverage is not applicable. No stale object is consumed. * +0 Confidentiality and integrity impacts are not established. * +0 No repeated release or refcount operation exists. * +0 No extra Availability point is awarded because the patch does not demonstrate a new host-wide crash, panic, persistent outage, or device-reset failure. 3. Reachability analysis The observed sequence requires an already wedged Xe device, a killed queue, a kernel-submitted GSC proxy job timeout, and driver unbind or rebind teardown. The supplied context identifies the reproducer as an IGT test that wedges the device and rebinds the driver. Driver unbind and rebind are host-administrative operations in normal Linux deployments. Therefore HostAdminRequired is YES for the complete supplied reproduction path. No evidence establishes that an ordinary logged-in user, DRM master, compositor, delegated graphics service, or namespace-scoped capability can perform the complete wedging and driver-rebind sequence. No network path, namespace-scoped path, special external device input path, or attacker-controlled firmware input is established. 4. Primitive and severity interpretation The exact defect is incorrect interpretation of timeout state during teardown. Killed queues bypass guc_submit_hint_wedged, leaving the local wedged variable false even when xe_device_wedged indicates that the device is already wedged. This causes an expected timeout during teardown to be treated as unexpected and emits a WARN that taints the kernel. This is neither an active structured-object lifetime bug nor fixed stale storage. There is no object free, post-free use, second put, refcount mutation, invalid memory access, or active-state retirement violation. The demonstrated consequence is diagnostic kernel tainting only. PrimitiveClass is NONE. ImportantCandidate is NO because there is no unresolved corruption, authorization, ownership, or security-boundary primitive. AutoDowngradeAllowed is YES because automatic deferral does not discard a meaningful security-relevant primitive. Operationally, this is a driver reliability and diagnostics cleanup for an already-failed GPU state. 5. One-sentence report phrase A drm xe teardown timeout on an already wedged device could incorrectly trigger a WARN and taint the kernel, but the patch indicates no memory corruption, security-boundary bypass, privilege escalation, or additional denial of service primitive. 6. Manual review recommendation NO MANUAL CHECK NEEDED The patch addresses a false unexpected-timeout warning after the device is already wedged. No meaningful security primitive is established. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: drm/xe: don't WARN on kernel job timeout when device already wedged [ Upstream Commit: 24d81b72992006f9c390f1fc85c7f991e6d06fd6 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=24d81b72992006f9c390f1fc85c7f991e6d06fd6 Changed files: drivers/gpu/drm/xe/xe_guc_submit.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=24d81b72992006f9c390f1fc85c7f991e6d06fd6 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-93248 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93248 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:H/PR:H/UI:N/S:U/C:N/I:N/A:N The Best / paranoid CVSS score: 0 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: 0 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).