CVE-2023-53225
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-04
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 3.16.57 (inc) to 3.17 (exc) |
| linux | linux_kernel | From 3.18.94 (inc) to 3.19 (exc) |
| linux | linux_kernel | From 4.1.50 (inc) to 4.2 (exc) |
| linux | linux_kernel | From 4.4.115 (inc) to 4.5 (exc) |
| linux | linux_kernel | From 4.9.80 (inc) to 4.10 (exc) |
| linux | linux_kernel | From 4.14.17 (inc) to 4.15 (exc) |
| linux | linux_kernel | From 4.15.1 (inc) to 5.10.180 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.111 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.28 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.2.15 (exc) |
| linux | linux_kernel | From 6.3 (inc) to 6.3.2 (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 occurs in the Linux kernel's spi: imx driver where the remove callback function returns early on error, causing DMA resources not to be released properly. This results in a permanent resource leak because the cleanup is skipped and not retried later. The fix ensures that hardware disabling is only skipped if waking the device fails, preventing the resource leak.
How can this vulnerability impact me? :
The vulnerability can lead to a permanent leak of DMA resources in the system, which may degrade system performance or stability over time due to unreleased resources accumulating.