CVE-2026-43105
Memory Leak in Linux Kernel DRM VC4 Driver
Publication date: 2026-05-06
Last updated on: 2026-05-11
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.24 (exc) |
| linux | linux_kernel | From 6.19 (inc) to 6.19.14 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.83 (exc) |
| linux | linux_kernel | From 4.5 (inc) to 6.6.136 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory leak in the Linux kernel's drm/vc4 component. Specifically, the BO (Buffer Object) array allocated during the hang state is not properly freed, which means memory that should be released remains allocated. The issue occurs because the BO array is allocated with kzalloc() in the function vc4_save_hang_state() but is never freed in vc4_free_hang_state(). The fix involves adding the missing kfree() call to free the BO array before freeing the hang state structure.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability impact me? :
The impact of this vulnerability is a memory leak in the Linux kernel, which can lead to increased memory usage over time. This could potentially degrade system performance or cause resource exhaustion if the hang state occurs frequently and the leaked memory accumulates. However, there is no indication that this vulnerability leads to privilege escalation or direct security breaches.