From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-68267][MODERATE 7.0] drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists [ Upstream Date: Mon, 10 Aug 2026 20:00:49 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-68267 X-AL-KERNEL-Priority: MODERATE 7.0 X-AL-KERNEL-Severity: MODERATE 7.0 X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: YES X-AL-KERNEL-ActionableScore: 6 X-AL-KERNEL-ActionableScore-Lower: 5 X-AL-KERNEL-Commit: 9852aa87ecba95d7bf9fb94a9d6c4f69312c9682 List-Id: CVE: CVE-2026-68267 Priority: MODERATE 7.0 AL-KERNEL base severity: MODERATE KPANIC flag: YES Patch: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists [ Upstream Commit: 9852aa87ecba95d7bf9fb94a9d6c4f69312c9682 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9852aa87ecba95d7bf9fb94a9d6c4f69312c9682 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68267 Analysis date: Mon, 10 Aug 2026 20:00:49 -0400 ActionableScore: 6 ActionableScore lower bound: 5 Actionable bucket: Actionable Moderate at minimum Manual review required: YES Summary: A local user with GPU render access may reach Intel Xe OA MMIO registers that were incorrectly whitelisted for nonprivileged access, causing a local GPU register permission bypass with plausible low confidentiality and integrity impact. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-68267 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68267 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 7.0 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-68267 MODERATE CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L';CWE-284;CWE-269;CWE-732;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N';BEST CVSS score: '5.3';DESCR 'OA MMIO trigger and status registers in the Intel Xe driver were incorrectly placed in the nonprivileged register whitelist. A local user able to submit GPU work through the render node or an equivalent GPU interface could gain access to registers that should remain denied by default after probe, gt reset, resume, or engine reset. For the CVSS the PR:L is used because reliable triggering requires local access to a GPU execution interface, but not full administrator privileges. The issue is not network reachable and there is no evidence of kernel memory corruption or a direct privilege escalation primitive. Impact is mainly a local access control bypass with possible low confidentiality and integrity impact through unauthorized OA register access. For the paranoid score, choose the highest still-defensible interpretation supported by the bug class and patch context, with preference for manual-review sensitivity over autoclosed false negatives.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 6) SKIP CVE-2026-68267 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 828a8eaf37c3fac6ba048995f55f1647a4ac542d YES NO NO unknown MAYBE SIMPLEFIX HARDWARE KPANIC INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=6 ActionableScoreLower=5 ## 1. ActionableScore * Conservative score: 5 * Paranoid score: 6 * Final recommended bucket: **Actionable Moderate at minimum**:: ## 2. Signal breakdown * Local unprivileged trigger: +1. A local user with access to the Intel Xe render node or equivalent GPU submission interface may be able to reach nonprivileged GPU register access paths. * Security-boundary bypass with practical sensitive-object access: +2. The patch explicitly states that unconditionally whitelisting OA registers is a security violation, meaning nonprivileged GPU contexts could access registers that should remain denied. * Confidentiality impact plausible: +1. OA registers are related to observability and performance monitoring, so unauthorized reads may expose low-grade performance or execution-state information. * Integrity impact plausible: +1. The trigger register was whitelisted with RW access, so unauthorized writes may influence OA behavior or GPU performance-monitoring state. * Broad or common local exposure, paranoid only: +1. Intel GPU render nodes are commonly exposed to local users on systems with affected Xe hardware, although the exact impact remains hardware and deployment dependent. No memory-corruption signal is counted. No LPE signal is counted. No remote/network signal is counted. ## 3. Reachability analysis The likely attacker is a local user or sandboxed process with access to the DRM render device. Full administrator privileges are not required if the render node is available to the user. Containers may matter if the GPU device is passed through or exposed to container workloads. The path is not network reachable. The issue depends on affected Intel Xe hardware and driver versions where OA MMIO trigger support is present, but this is not a rare debug-only path once the relevant GPU stack is deployed. Call-site confidence: medium. The patch directly changes the nonprivileged register whitelist entries, but the full runtime register access path is not included in the provided diff. ## 4. Severity interpretation This behaves more like an actionable Moderate than an ordinary Low or auto-close Moderate. The issue is an access-control failure in a GPU register whitelist, not a UAF, OOB write, refcount bug, or arbitrary kernel memory corruption. Realistic exploitation evidence supports unauthorized access to privileged OA registers, with plausible low confidentiality and integrity impact. The paranoid score is higher because hardware register semantics may have security-relevant side effects that are not fully visible from the small patch. ## 5. One-sentence report phrase A local user with GPU render access may reach Intel Xe OA MMIO registers that were incorrectly whitelisted for nonprivileged access, causing a local GPU register permission bypass with plausible low confidentiality and integrity impact. ## 6. Manual review recommendation MANUAL CHECK REQUIRED. The patch explicitly calls the behavior a security violation, and the exact impact depends on OA register semantics and affected Intel Xe hardware behavior. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists [ Upstream Commit: 9852aa87ecba95d7bf9fb94a9d6c4f69312c9682 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9852aa87ecba95d7bf9fb94a9d6c4f69312c9682 Changed files: drivers/gpu/drm/xe/xe_reg_whitelist.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=9852aa87ecba95d7bf9fb94a9d6c4f69312c9682 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-68267 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68267 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:L/PR:L/UI:N/S:U/C:L/I:L/A:N The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L The Best / paranoid CVSS score: 5.3 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: 5 Paranoid ActionableScore: 6 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: YES Published priority for this report (same as in Subject): MODERATE 7.0 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).