CVE-2023-53174
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-02
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 2.6.26 (inc) to 4.14.323 (exc) |
| linux | linux_kernel | From 4.15 (inc) to 4.19.292 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.254 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.191 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.127 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.46 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.4.11 (exc) |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
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 possible memory leak in the Linux kernel's SCSI core. Specifically, if the function device_add() fails, the memory allocated for the device name by dev_set_name() is not properly freed. The fix involves calling put_device() to decrease the reference count, allowing the allocated name to be freed correctly, preventing the memory leak.
How can this vulnerability impact me? :
This vulnerability can lead to a memory leak in the Linux kernel, which over time could cause increased memory usage and potentially degrade system performance or stability if device_add() failures occur frequently.