CVE-2023-53308
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 4.9.206 (inc) to 4.10 (exc) |
| linux | linux_kernel | From 4.14.158 (inc) to 4.14.316 (exc) |
| linux | linux_kernel | From 4.19.88 (inc) to 4.19.284 (exc) |
| linux | linux_kernel | From 5.3.15 (inc) to 5.4 (exc) |
| linux | linux_kernel | From 5.4.1 (inc) to 5.4.244 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.181 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.113 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.30 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.3.4 (exc) |
| linux | linux_kernel | 5.4 |
| linux | linux_kernel | 6.4 |
| linux | linux_kernel | 6.4 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-415 | The product calls free() twice on the same memory address. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's fec driver where, if the function pm_runtime_get() (called as pm_runtime_resume_and_get()) fails during device removal, the remove callback returns an error early. However, the driver core ignores this error and continues removing the device, leading to a resource leak. Additionally, resources allocated with devm are freed prematurely, so if a driver callback is called later, it may access freed memory causing a crash.
How can this vulnerability impact me? :
The vulnerability can cause resource leaks and potentially lead to system crashes due to use-after-free conditions when driver callbacks access freed resources. This can affect system stability and reliability.