Linux Kernel up to 6.6.127/6.12.74/6.18.13/6.19.3 amdgpu_acpi_enumerate_xcc memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability categorized as critical has been discovered in Linux Kernel up to 6.6.127/6.12.74/6.18.13/6.19.3. This affects the function amdgpu_acpi_enumerate_xcc. Executing a manipulation can lead to memory leak. This vulnerability is registered as CVE-2026-45947. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.6.127/6.12.74/6.18.13/6.19.3. This vulnerability affects the function amdgpu_acpi_enumerate_xcc. The manipulation with an unknown input leads to a memory leak vulnerability. The CWE definition for the vulnerability is CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. As an impact it is known to affect availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix memory leak in amdgpu_acpi_enumerate_xcc() In amdgpu_acpi_enumerate_xcc(), if amdgpu_acpi_dev_init() returns -ENOMEM, the function returns directly without releasing the allocated xcc_info, resulting in a memory leak. Fix this by ensuring that xcc_info is properly freed in the error paths. Compile tested only. Issue found using a prototype static analysis tool and code review.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-45947 since 05/13/2026. There are known technical details, but no exploit is available.

Upgrading to version 6.6.128, 6.12.75, 6.18.14 or 6.19.4 eliminates this vulnerability. Applying the patch e87c73a80a12d337cf5f493c0956f6c2c9eafd80/18a7bbd11f17a7cd4c42fd5955d3675d68c692df/d1370ef2ecf7d4df25e3e1e430cd191b1e7f8596/7e4b612fe7a960d610c20260c9ee220bddd1b215/c9be63d565789b56ca7b0197e2cb78a3671f95a8 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.128/6.12.75/6.18.14/6.19.4
Patch: e87c73a80a12d337cf5f493c0956f6c2c9eafd80/18a7bbd11f17a7cd4c42fd5955d3675d68c692df/d1370ef2ecf7d4df25e3e1e430cd191b1e7f8596/7e4b612fe7a960d610c20260c9ee220bddd1b215/c9be63d565789b56ca7b0197e2cb78a3671f95a8

Timelineinfo

05/13/2026 CVE reserved
05/27/2026 +14 days Advisory disclosed
05/27/2026 +0 days VulDB entry created
06/16/2026 +20 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-45947 (🔒)
GCVE (CVE): GCVE-0-2026-45947
GCVE (VulDB): GCVE-100-366220

Entryinfo

Created: 05/27/2026 17:16
Updated: 06/16/2026 08:23
Changes: 05/27/2026 17:16 (58), 06/16/2026 08:23 (10)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!