CVE-2023-53316
BaseFortify
Publication date: 2025-09-16
Last updated on: 2025-12-01
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.10 (inc) to 5.10.188 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.121 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.39 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.3.13 (exc) |
| linux | linux_kernel | From 6.4 (inc) to 6.4.4 (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 is in the Linux kernel's drm/msm/dp component. It occurs because the unbind operation unregisters and cleans up submodules after the DP controller is being removed, but the memory for those submodules has already been freed. This leads to use-after-free errors. The fix changes the order of operations to free resources only after unregistering them, preventing these use-after-free issues.
How can this vulnerability impact me? :
The vulnerability can cause use-after-free errors in the Linux kernel's DP component, which may lead to system instability, crashes, or potential exploitation by attackers to execute arbitrary code or cause denial of service.