CVE-2023-53636
BaseFortify
Publication date: 2025-10-07
Last updated on: 2026-02-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.3 (inc) to 6.3.2 (inc) |
| microchip | linux_kernel | * |
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 a use-after-free (UAF) issue in the Linux kernel's microchip clock driver auxiliary device release callback. It occurs because the auxiliary device is not torn down in the correct order. Specifically, if auxiliary_device_add() fails, the release callback is called twice, leading to a use-after-free condition. The problem is similar to a previous bug in the peci CPU driver. The fix involves moving auxiliary_device_uninit() to the unregister callback to prevent the double release and UAF.
How can this vulnerability impact me? :
This vulnerability can lead to a use-after-free condition in the kernel, which may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or escalate privileges if exploited. The exact impact depends on the environment and how the vulnerable driver is used.