CVE-2023-53562
BaseFortify
Publication date: 2025-10-04
Last updated on: 2026-03-21
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 5.11 |
| linux | linux_kernel | From 6.2 (inc) to 6.2.16 (exc) |
| linux | linux_kernel | 5.11 |
| linux | linux_kernel | 5.11 |
| linux | linux_kernel | 5.11 |
| linux | linux_kernel | 5.11 |
| linux | linux_kernel | 5.11 |
| linux | linux_kernel | From 6.3 (inc) to 6.3.3 (exc) |
| linux | linux_kernel | From 4.19.169 (inc) to 4.20 (exc) |
| linux | linux_kernel | From 5.10.9 (inc) to 5.11 (exc) |
| linux | linux_kernel | From 5.11.1 (inc) to 6.1.29 (exc) |
| linux | linux_kernel | From 5.4.91 (inc) to 5.5 (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 VRAM (video RAM) leak in the Linux kernel's drm/msm driver. It occurs when a subcomponent fails to bind, and the VRAM buffer is not properly released, leading to a resource leak.
How can this vulnerability impact me? :
The vulnerability can cause a VRAM leak, which may lead to increased memory usage and potentially degrade system performance or stability over time if the leaked resources are not freed.
What immediate steps should I take to mitigate this vulnerability?
Apply the patch that fixes the VRAM leak on bind errors in the drm/msm component of the Linux kernel. This patch ensures that the VRAM buffer is released properly even if a subcomponent fails to bind. Refer to the patch at https://patchwork.freedesktop.org/patch/525094/ for details and update your kernel accordingly.