CVE-2023-53388
BaseFortify
Publication date: 2025-09-18
Last updated on: 2025-12-11
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.7 (inc) to 4.19.276 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.235 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.173 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.99 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.16 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.2.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's Mediatek DRM driver where, if the mtk_drm_bind() function fails, the drm_device object is destroyed but a pointer to it remains in the private object. If a suspend operation is triggered afterward, this dangling pointer is used, causing a kernel panic. The fix involves cleaning the pointer when destroying the object on the error path to prevent this issue.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to panic (crash) if a suspend operation occurs after a failed bind in the Mediatek DRM driver. This can lead to system instability, unexpected reboots, or denial of service on affected systems.