From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-45976][LOW] drm/amdgpu: Fix memory leak in amdgpu_ras_init() [ Upstream Date: Sat, 01 Aug 2026 11:29:57 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-45976 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: f8a5426652bdadd4a5cb48326d48abbdfebe8153 List-Id: CVE: CVE-2026-45976 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: drm/amdgpu: Fix memory leak in amdgpu_ras_init() [ Upstream Commit: f8a5426652bdadd4a5cb48326d48abbdfebe8153 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f8a5426652bdadd4a5cb48326d48abbdfebe8153 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45976 Analysis date: Sat, 01 Aug 2026 11:29:57 -0400 ActionableScore: 0 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate / Low-like Manual review required: NO Summary: A memory leak in amdgpu_ras_init() can occur when amdgpu_nbio_ras_sw_init() fails after allocating the RAS context, but exploitation is limited to a privileged local driver initialization error path and has no evidence of memory corruption or privilege escalation. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-45976 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45976 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-45976 LOW 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:L';*CWE-401;*CWE-772;CWE-703;BEST CVSS score: '1.9';DESCR 'A memory leak in amdgpu_ras_init() can occur when amdgpu_nbio_ras_sw_init() fails after the RAS context has already been allocated. The function returned the error directly and skipped the cleanup path, leaving the allocated context unreachable. For the CVSS the PR:H because reliable triggering normally requires administrative control over GPU driver load, unload, reset, or a specific hardware failure condition during driver initialization. The issue is not network reachable. Impact is limited to local denial of service through resource leakage, with no evidence of UAF, OOB access, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0) MAYBE SIMPLEFIX LEAK HARDWARE TEST - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=0 ## 1. ActionableScore * Conservative score: 0 * Paranoid score: 0 * Final recommended bucket: **Ordinary Moderate / Low-like** ## 2. Signal breakdown Triggered signals: * Requires admin/root/CAP_* in typical deployments: -2 Triggering this path normally requires GPU driver initialization, reload, reset, or a hardware/firmware error during privileged driver setup. * Rare AND difficult-to-reach subsystem/configuration: -1 The leak occurs only on a specific AMDGPU RAS initialization error path when amdgpu_nbio_ras_sw_init() fails. Not triggered: * No remote reachable signal. The path is not network exposed. * No local unprivileged trigger is evident. * No generic memory corruption. The patch fixes a missed cleanup, not UAF, OOB, double free, type confusion, or overwrite. * No strong DoS signal. The leak is a single error-path allocation leak, not an immediate or reliable system-wide crash. * No confidentiality or integrity impact. ## 3. Reachability analysis The bug is reachable only during AMDGPU RAS initialization after the RAS context allocation has succeeded and amdgpu_nbio_ras_sw_init() then fails. In normal deployments, users cannot directly trigger this without administrative control over driver load/unload/reset or without a specific device/firmware failure condition. Containers or namespaces do not meaningfully lower the privilege requirement unless they are already delegated host GPU driver management, which is atypical. The affected code is not remotely reachable and not part of a common unprivileged kernel data-plane API. Call-site confidence: high, because the provided patch shows the exact error path and cleanup label consequence. ## 4. Severity interpretation This behaves like a low-risk resource leak, not an Important-class vulnerability. The theoretical impact is local availability degradation if the error path can be forced repeatedly, but the patch does not show memory corruption, stale pointer use, attacker-controlled reclaim, sensitive object exposure, or privilege escalation. Realistic exploitation evidence is weak because the condition depends on privileged driver lifecycle control or unusual hardware initialization failure. ## 5. One-sentence report phrase A memory leak in amdgpu_ras_init() can occur when amdgpu_nbio_ras_sw_init() fails after allocating the RAS context, but exploitation is limited to a privileged local driver initialization error path and has no evidence of memory corruption or privilege escalation. ## 6. Manual review recommendation NO MANUAL CHECK NEEDED This is a straightforward cleanup-path memory leak with low practical exploitability, no remote exposure, no unprivileged trigger, and no concrete corruption primitive. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: drm/amdgpu: Fix memory leak in amdgpu_ras_init() [ Upstream Commit: f8a5426652bdadd4a5cb48326d48abbdfebe8153 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f8a5426652bdadd4a5cb48326d48abbdfebe8153 Changed files: drivers/gpu/drm/amd/amdgpu/amdgpu_ras.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=f8a5426652bdadd4a5cb48326d48abbdfebe8153 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-45976 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45976 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:L The Best / paranoid CVSS score: 1.9 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).