From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-80541][MODERATE REGULAR] drm/amdgpu: validate GEM_CREATE domain combinations Date: Wed, 26 Aug 2026 13:37:41 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-80541 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: 4 X-AL-KERNEL-ActionableScore-Lower: 3 X-AL-KERNEL-Commit: 5c73485af7ad9c3ae592db3481f370bc07705391 List-Id: CVE: CVE-2026-80541 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: drm/amdgpu: validate GEM_CREATE domain combinations Commit: 5c73485af7ad9c3ae592db3481f370bc07705391 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5c73485af7ad9c3ae592db3481f370bc07705391 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80541 Analysis date: Wed, 26 Aug 2026 13:37:41 -0400 ActionableScore: 4 ActionableScore lower bound: 3 Actionable bucket: Borderline Moderate / 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-80541 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80541 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-80541 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:N/I:N/A:H';*CWE-20;CWE-617;CWE-754;BEST CVSS score: '5.5';DESCR 'AMDGPU GEM_CREATE accepted invalid domain combinations because it checked domain bits against AMDGPU_GEM_DOMAIN_MASK but did not validate whether the selected domains can be used together. A local userspace process with access to the amdgpu DRM device could combine CPU/GTT/VRAM with special domains such as DOORBELL, GDS, GWS, or OA, causing amdgpu_bo_placement_from_domain to exceed AMDGPU_BO_MAX_PLACEMENTS and hit BUG_ON(). For the CVSS the PR:L is used because reliable triggering requires local code execution with access to the DRM device node, but not full administrator privileges. The issue is not network reachable and affects the local graphics control path rather than packet or remote protocol processing. Impact is denial of service via kernel BUG or crash, with no supported evidence of information disclosure or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline Moderate / manual review recommended (with actual score 4) SKIP CVE-2026-80541 UNKNOWN SKIP No affected files built, so skip this CVE NO - - unknown MAYBE HARDWARE INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=4 ActionableScoreLower=3 1. ActionableScore * Conservative score: 3 * Paranoid score: 4 * Final recommended bucket: **Borderline Moderate / manual review recommended** 2. Signal breakdown * Local unprivileged trigger: +1. The affected path is `amdgpu_gem_create_ioctl()`, reachable by local users with access to the AMDGPU DRM device node. * Reliable kernel crash / strong DoS: +1. Invalid GEM domain combinations can make `amdgpu_bo_placement_from_domain()` exceed `AMDGPU_BO_MAX_PLACEMENTS` and hit `BUG_ON()`. * Broad/default/common subsystem exposure: +1. DRM render nodes are commonly exposed to local desktop, GPU, or compute users on systems with AMD GPUs. * Availability impact realistic: +1 in paranoid scoring only. The trigger appears simple and can cause a kernel BUG/crash, but this partly overlaps with the strong DoS signal, so it is not counted in the conservative score. * No generic memory corruption signal. The patch shows validation preventing a BUG_ON path, not UAF, OOB write, double free, type confusion, arbitrary write, or page-cache corruption. * No LPE signal. There is no supported evidence of attacker-controlled memory corruption or privilege escalation. 3. Reachability analysis A local userspace process can trigger the bug through the AMDGPU GEM create ioctl if it has access to the relevant DRM device node. This usually does not require full administrator privileges because render nodes are often accessible to logged-in users or GPU workloads. Containers may matter if GPU device nodes are passed through, but the issue is not remotely reachable over the network. The path is configuration and hardware dependent because it requires AMDGPU, but it is not a rare debug-only path on affected systems. Call-site confidence: high, because the changed validation is directly in `amdgpu_gem_create_ioctl()` and the commit describes the downstream `BUG_ON()` condition. 4. Severity interpretation This behaves like an actionable local DoS rather than an Important-class memory corruption vulnerability. The theoretical impact is a kernel crash through a reachable userspace ioctl. Realistic exploitation evidence supports availability impact only. The patch does not support confidentiality impact, integrity impact, or privilege escalation. The issue should not be auto-closed purely as low risk because it is local-user reachable and hits a kernel BUG in a common GPU ioctl path. 5. One-sentence report phrase AMDGPU GEM_CREATE did not validate domain combinations, allowing a local user with DRM device access to combine normal and special domains and trigger a BUG_ON in buffer placement, causing a local kernel DoS without evidence of information disclosure or privilege escalation. 6. Manual review recommendation MANUAL CHECK REQUIRED. YES REQUIRES MANUAL CHECK because this is a local user reachable kernel BUG through a common DRM ioctl path, although current evidence supports DoS only rather than memory corruption or LPE. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: drm/amdgpu: validate GEM_CREATE domain combinations Commit: 5c73485af7ad9c3ae592db3481f370bc07705391 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5c73485af7ad9c3ae592db3481f370bc07705391 Commit description: AMDGPU_GEM_CREATE checked domain bits against AMDGPU_GEM_DOMAIN_MASK, but did not validate domain combinations. Userspace could combine CPU|GTT|VRAM with DOORBELL, GDS, GWS, or OA, making amdgpu_bo_placement_from_domain() exceed AMDGPU_BO_MAX_PLACEMENTS and hit BUG_ON(). Allow combinations only within CPU/GTT/VRAM, and require non-CPU/GTT/ VRAM domains to be specified one at a time. Return -EINVAL for invalid combinations in amdgpu_gem_create_ioctl(). v2: Rename helper from amdgpu_gem_domain_valid() to amdgpu_gem_are_domains_valid() (Christian) Signed-off-by: Candice Li Reviewed-by: Christian König Signed-off-by: Alex Deucher (cherry picked from commit db39852 ) Cc: stable@vger.kernel.org Signed-off-by: Greg Kroah-Hartman Changed files: drivers/gpu/drm/amd/amdgpu/amdgpu_gem.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=5c73485af7ad9c3ae592db3481f370bc07705391 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80541 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80541 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: 3 Paranoid ActionableScore: 4 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).