From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98510][MODERATE REGULAR] drm/xe/vm: nuke PTs only after unlinking contested VMAs [ Upstream Date: Sat, 24 Oct 2026 03:26:51 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98510 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: 2 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 70fddc065ac80845ffd33095b3635d59883cf7e6 List-Id: CVE: CVE-2026-98510 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: drm/xe/vm: nuke PTs only after unlinking contested VMAs [ Upstream Commit: 70fddc065ac80845ffd33095b3635d59883cf7e6 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=70fddc065ac80845ffd33095b3635d59883cf7e6 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98510 Analysis date: Sat, 24 Oct 2026 03:26:51 -0400 ActionableScore: 2 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: A local Xe DRM client can race VM teardown with shared-BO eviction, causing an obsolete VMA association to drive a NULL page-table-root dereference and kernel crash. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98510 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98510 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-98510 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-98510 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=1 LEGACY=MODERATE RESULT=DIFF (final Legacy and Aegis differ; FINAL: MODERATE, Aegis: MODERATE_KPANIC) 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-362;**CWE-476;*CWE-664;BEST CVSS score: '4.7';DESCR 'A teardown race in xe_vm_close_and_put can leave contested external BO VMAs linked after vm pt_root has already been destroyed. Concurrent eviction of a shared BO can walk one of these VMAs and reach xe_vm_invalidate_vma and xe_pt_zap_ptes, where the NULL page table root is dereferenced through pt level. For the CVSS the PR:L value is selected because reliable triggering requires a local process with access to the Xe DRM device and control of a VM and shared BO workload. AC:H reflects the required race between VM teardown and BO eviction. The demonstrated primitive is a NULL pointer dereference causing a kernel oops or panic, with no supported UAF, OOB access, information leak, or write primitive. The issue is not directly network reachable and depends on affected Intel Xe hardware and driver use. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 4.7 and the production ActionableScore returned 2 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to MODERATE because the CVSS score, vector or bug class threshold rule was applied. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH and V41_INHERITED_KPANIC_PROMOTION_BLOCKED and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 2.5 and ActionableScore 1 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was MODERATE_KPANIC. The models disagreed but the aggregation rules retained the production result. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2) MAYBE LOCK NULLPTR INIT SIMPLEFIX RACE HARDWARE DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH V41_INHERITED_KPANIC_PROMOTION_BLOCKED MANUAL_REVIEW_REQUIRED - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=NO NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES RequiresHostUID0=NO AuthorizationDecisionBypass=NO ProtectedResourceImpact=NONE B4PendingReview=NO B4PendingConfirmed=NO 1. ActionableScore * Raw base score: 2. * Conservative score: 2; no floor or cap applied. * Raw paranoid score: 2. * Paranoid score: 2; no defensible stronger primitive is shown. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 Reliable kernel crash/strong DoS: concurrent BO eviction can reach `xe_pt_zap_ptes()` after `vm->pt_root` was destroyed, producing the reported NULL dereference. * +1 Local below-host-admin trigger: supplied evidence identifies a local Xe DRM client controlling a VM and shared-BO workload. * +1 Secondary index/reverse-association staleness: external-BO VMAs remain linked on `vm_bo->list.gpuva`, allowing the eviction walker to consume an association after its page-table state is gone. * -1 Hard race: successful triggering requires concurrent VM teardown and shared-BO eviction; supplied triage specifically characterizes this as AC:H. Not awarded: * No UAF: the supported terminal operation dereferences a NULL page-table root, not reclaimed storage. * No OOB write, attacker-directed write, controlled reclaim, disclosure, or authorization bypass. * NEW52/B5-R does not apply: there is no retry-accumulated heap OOB write. * No extra availability point for the same oops/panic. * No hardware rarity penalty: affected Xe hardware is required, but it is not shown to be rare or physical-attacker-only. 3. Reachability analysis A local process with access to the affected Xe DRM device can create the VM/shared-BO workload and race VM closure against BO eviction. The supplied evidence supports below-host-admin device access, but not ordinary access independent of DRM device-node permissions. No capability or user/network-namespace mechanism is involved, and no prior host-admin configuration beyond an available affected device/driver is shown. 4. Primitive and severity reading The exact defect is teardown ordering: page tables are destroyed while contested external-BO VMAs remain discoverable through the BO association list. A concurrent eviction walker follows that association and reaches a NULL `pt_root`. This is active-state inconsistency culminating in a NULL dereference, classified CLASS_C rather than a real UAF or corruption primitive. The shown effect is host kernel oops/panic. Non-crash memory corruption, useful stale-object reuse, confidentiality/integrity impact, and privilege escalation are unsupported. Therefore this is not an Important candidate and can be downgraded to ordinary Moderate after review. 5. One-sentence report phrase A local Xe DRM client can race VM teardown with shared-BO eviction, causing an obsolete VMA association to drive a NULL page-table-root dereference and kernel crash. 6. Manual review advice MANUAL CHECK RECOMMENDED Confirm DRM node exposure and whether the affected product converts the oops into a host-wide panic. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: drm/xe/vm: nuke PTs only after unlinking contested VMAs [ Upstream Commit: 70fddc065ac80845ffd33095b3635d59883cf7e6 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=70fddc065ac80845ffd33095b3635d59883cf7e6 Changed files: drivers/gpu/drm/xe/xe_vm.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=70fddc065ac80845ffd33095b3635d59883cf7e6 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98510 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98510 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: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: unknown 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: 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).