CVE-2023-53003

published 27 Mar 2025 · updated 11 May 2026

EDAC/qcom: Do not pass llcc_driv_data as edac_device_ctl_info's pvt_info

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 66e10d5f399629ef7877304d9ba2b35d0474e7eb, Kernel 6f0351d0c311951b8b3064db91e61841e85b2b96, Kernel 76d9ebb7f0bc10fbc78b6d576751552edf743968 and 2 more.

In the Linux kernel, the following vulnerability has been resolved: EDAC/qcom: Do not pass llcc_driv_data as edac_device_ctl_info's pvt_info The memory for llcc_driv_data is allocated by the LLCC driver. But when it is passed as the private driver info to the EDAC core, it will get freed during the qcom_edac driver release. So when the qcom_edac driver gets probed again, it will try to use the freed data leading to the use-after-free bug. Hence, do not pass llcc_driv_data as pvt_info but rather reference it using the platform_data pointer in the qcom_edac driver.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.20, >=27450653f1db0b9d5b5048a246c850c52ee4aa61 <66e10d5f399629ef7877304d9ba2b35d0474e7eb, >=27450653f1db0b9d5b5048a246c850c52ee4aa61 <6f0351d0c311951b8b3064db91e61841e85b2b96, >=27450653f1db0b9d5b5048a246c850c52ee4aa61 <76d9ebb7f0bc10fbc78b6d576751552edf743968, >=27450653f1db0b9d5b5048a246c850c52ee4aa61 <977c6ba624f24ae20cf0faee871257a39348d4a9, >=27450653f1db0b9d5b5048a246c850c52ee4aa61 <bff5243bd32661cf9ce66f6d9210fc8f89bda14566e10d5f399629ef7877304d9ba2b35d0474e7eb, 6f0351d0c311951b8b3064db91e61841e85b2b96, 76d9ebb7f0bc10fbc78b6d576751552edf743968, 977c6ba624f24ae20cf0faee871257a39348d4a9, bff5243bd32661cf9ce66f6d9210fc8f89bda145

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2023-53003 severity on Zeptric[![CVE-2023-53003](https://zeptric.io/badge/cve/CVE-2023-53003.svg)](https://zeptric.io/cve/CVE-2023-53003)