PatchSiren cyber security CVE debrief
CVE-2026-45947 Linux CVE debrief
A memory leak vulnerability exists in the Linux kernel's AMDGPU driver, specifically within the `amdgpu_acpi_enumerate_xcc()` function. When `amdgpu_acpi_dev_init()` returns `-ENOMEM` (indicating memory allocation failure), the function exits directly without freeing the previously allocated `xcc_info` structure, resulting in a resource leak. This issue was identified through prototype static analysis tooling and code review, with a fix implemented to ensure proper deallocation in error paths. The vulnerability affects kernel-level graphics driver operations and could contribute to memory exhaustion under error conditions. No CVSS score has been assigned; NVD status is 'Awaiting Analysis'.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-05-27
- Original CVE updated
- 2026-06-16
- Advisory published
- 2026-05-27
- Advisory updated
- 2026-06-16
Who should care
Linux system administrators running kernels with AMDGPU driver support; organizations with AMD GPU deployments in server or workstation environments; kernel security teams tracking memory management defects
Technical summary
The `amdgpu_acpi_enumerate_xcc()` function in the Linux kernel's AMDGPU DRM driver allocates memory for an `xcc_info` structure. If a subsequent call to `amdgpu_acpi_dev_init()` fails with `-ENOMEM`, the function returns immediately without freeing the allocated `xcc_info`, causing a memory leak. The fix ensures proper cleanup of `xcc_info` in all error paths. The vulnerability is compile-tested only per the commit message, with discovery attributed to prototype static analysis tooling and code review.
Defensive priority
medium
Recommended defensive actions
- Apply kernel patches from stable Linux kernel releases containing the fix commits
- Monitor NVD for CVSS scoring and analysis updates once vulnerability assessment is completed
- Review local kernel configurations for AMDGPU driver usage and prioritize patching on systems with AMD graphics hardware
- Consider enabling kernel memory leak detection mechanisms (KASAN, KMEMLEAK) in test environments to identify similar issues
Evidence notes
Vulnerability description sourced from official CVE record and NVD entry. Fix commits identified in Linux kernel stable tree. Issue discovered via prototype static analysis tool and manual code review per CVE description. Vendor attribution to Linux kernel inferred from source code references; explicit vendor field marked as low-confidence 'Unknown Vendor' in source data.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-45947 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-45947
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-45947 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-45947
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/18a7bbd11f17a7cd4c42fd5955d3675d68c692df
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/7e4b612fe7a960d610c20260c9ee220bddd1b215
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/c9be63d565789b56ca7b0197e2cb78a3671f95a8
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/d1370ef2ecf7d4df25e3e1e430cd191b1e7f8596
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/e87c73a80a12d337cf5f493c0956f6c2c9eafd80
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.