From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-45947][LOW] drm/amdgpu: Fix memory leak in amdgpu_acpi_enumerate_xcc() [ Upstream Date: Sat, 01 Aug 2026 11:41:26 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-45947 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: 1 X-AL-KERNEL-ActionableScore-Lower: 0 X-AL-KERNEL-Commit: e87c73a80a12d337cf5f493c0956f6c2c9eafd80 List-Id: CVE: CVE-2026-45947 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: drm/amdgpu: Fix memory leak in amdgpu_acpi_enumerate_xcc() [ Upstream Commit: e87c73a80a12d337cf5f493c0956f6c2c9eafd80 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e87c73a80a12d337cf5f493c0956f6c2c9eafd80 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45947 Analysis date: Sat, 01 Aug 2026 11:41:26 -0400 ActionableScore: 1 ActionableScore lower bound: 0 Actionable bucket: Ordinary Moderate / Low-like. Auto-close candidate Manual review required: YES Summary: A small memory leak in amdgpu_acpi_enumerate_xcc() can occur on an ENOMEM error path during AMDGPU ACPI XCC enumeration, but triggering is privileged and hardware or initialization dependent, with only limited availability impact. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-45947 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45947 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: YES A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-45947 LOW 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:H/UI:N/S:U/C:N/I:N/A:L';*CWE-401;*CWE-772;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '2.3';DESCR 'A memory leak in amdgpu_acpi_enumerate_xcc occurs when amdgpu_acpi_dev_init returns ENOMEM and the function exits without freeing xcc_info. This is an error path during AMD GPU ACPI XCC enumeration and does not show a UAF, OOB access, arbitrary write, or information leak primitive. For the CVSS the PR:H is used because triggering this path typically requires administrative control over GPU driver probing or system configuration, and the leak occurs only in an ENOMEM error path. The issue is not network reachable. Impact is limited availability risk from a small unreleased allocation and is unlikely to cause immediate system wide DoS.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like. Auto-close candidate (with actual score 1) MAYBE NOMEMCHK LEAK ERRORPATH UAF HARDWARE TEST - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 ActionableScoreLower=0 ## 1. ActionableScore * Conservative score: 0 * Paranoid score: 1 * Final recommended bucket: **Ordinary Moderate / Low-like. Auto-close candidate** ## 2. Signal breakdown * Availability impact realistic: +1 only in paranoid interpretation. The bug is a memory leak, but only on the ENOMEM error path during AMDGPU ACPI XCC enumeration. * Requires admin/root/system-level control in typical deployments: -2. Realistic triggering requires driver probing, GPU initialization, ACPI/platform configuration influence, or system-level fault injection. * Rare and difficult-to-reach condition: -1. The leak requires amdgpu_acpi_dev_init() to return ENOMEM after xcc_info was allocated. * No generic memory corruption: +0. The patch shows a missing kfree(), not UAF, double free, OOB write, type confusion, stale callback, or refcount misuse. * No privilege escalation plausible: +0. There is no reclaim, overwrite, object confusion, credential boundary bypass, or attacker-controlled reuse. * No reliable strong DoS: +0. The leak appears small and error-path-bound, with no evidence that an unprivileged actor can repeat it enough to exhaust memory. ## 3. Reachability analysis The affected path is AMDGPU ACPI XCC enumeration during GPU driver or platform initialization. It is not network reachable and is not normally exposed to an unprivileged local user. Namespaces or containers do not materially lower the privilege requirement because the relevant path is tied to host hardware probing and kernel driver initialization. Realistic exploitation would require administrative control, fault injection, unusual memory pressure at a precise initialization path, or influence over platform firmware/device configuration. Call-site confidence: medium. The provided patch shows the immediate error path and cleanup behavior, but not all callers of amdgpu_acpi_enumerate_xcc(). ## 4. Severity interpretation This behaves like a Low or ordinary Moderate resource-leak issue, not an Important-class vulnerability. The theoretical impact is limited availability degradation from unreleased memory. The realistic evidence supports only a small privileged error-path leak, with no concrete memory corruption primitive, no confidentiality impact, no integrity impact, and no practical privilege-escalation path. ## 5. One-sentence report phrase A small memory leak in amdgpu_acpi_enumerate_xcc() can occur on an ENOMEM error path during AMDGPU ACPI XCC enumeration, but triggering is privileged and hardware or initialization dependent, with only limited availability impact. ## 6. Manual review recommendation NO MANUAL CHECK NEEDED. NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED. This can be handled as an auto-close candidate unless product-specific evidence shows unprivileged repeated triggering or system-wide memory exhaustion. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: drm/amdgpu: Fix memory leak in amdgpu_acpi_enumerate_xcc() [ Upstream Commit: e87c73a80a12d337cf5f493c0956f6c2c9eafd80 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e87c73a80a12d337cf5f493c0956f6c2c9eafd80 Changed files: drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.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=e87c73a80a12d337cf5f493c0956f6c2c9eafd80 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-45947 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45947 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:H/PR:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS score: 2.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: 0 Paranoid ActionableScore: 1 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).