CVE-2026-43104
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability described is a memory leak in the Linux kernel's drm/vc4 component. There is no information provided about any impact on data confidentiality, integrity, or availability that would relate to compliance with standards such as GDPR or HIPAA.
Since the vulnerability involves a memory leak without further details on data exposure or unauthorized access, it does not directly indicate an effect on compliance with common standards and regulations.
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's drm/vc4 component. Specifically, when the function vc4_save_hang_state() encounters an early return condition, it fails to free previously allocated memory called kernel_state. This results in a memory leak.
The fix involved adding the missing kfree() calls by consolidating the early return paths into a single place to ensure the allocated memory is properly freed.
How can this vulnerability impact me? :
The vulnerability causes a memory leak in the Linux kernel when certain error conditions occur in the drm/vc4 driver. Over time, this could lead to increased memory usage, potentially degrading system performance or causing instability if the leaked memory accumulates.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the drm/vc4 memory leak issue in the hang state error path has been fixed.
This fix involves adding missing kfree() calls to properly free allocated kernel memory in the vc4_save_hang_state() function.