0.0
NA
CVE-2023-52871
Qualcomm soc Linux Kernel Use-After-Free Vulnerability
Description

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: llcc: Handle a second device without data corruption Usually there is only one llcc device. But if there were a second, even a failed probe call would modify the global drv_data pointer. So check if drv_data is valid before overwriting it.

INFO

Published Date :

May 21, 2024, 4:15 p.m.

Last Modified :

Nov. 21, 2024, 8:40 a.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2023-52871 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
Solution
Updating the affected packages addresses the Qualcomm SOC Linux kernel vulnerability.
  • Update the affected Linux packages.
  • Update the kernel-livepatch package.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2023-52871 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2023-52871 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2023-52871 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2023-52871 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by af854a3a-2127-422b-91ae-364da2661108

    Nov. 21, 2024

    Action Type Old Value New Value
    Added Reference https://git.kernel.org/stable/c/1143bfb9b055897975aeaea254da148e19524493
    Added Reference https://git.kernel.org/stable/c/3565684309e54fa998ea27f37028d67cc3e1dff2
    Added Reference https://git.kernel.org/stable/c/5e5b85ea0f4bc484bfe4cc73ead51fa48d2366a0
    Added Reference https://git.kernel.org/stable/c/995ee1e84e8db7fa5dcdde7dfe0bd7bb6f9bbb8c
    Added Reference https://git.kernel.org/stable/c/cc1a1dcb411fe224f48553cfdcdfe6e61395b69c
    Added Reference https://git.kernel.org/stable/c/f0ef883cae309bc5e8cdfcdbc1b4822732ce20a8
    Added Reference https://git.kernel.org/stable/c/f1a1bc8775b26345aba2be278118999e7f661d3d
  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    May. 29, 2024

    Action Type Old Value New Value
  • CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    May. 21, 2024

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: soc: qcom: llcc: Handle a second device without data corruption Usually there is only one llcc device. But if there were a second, even a failed probe call would modify the global drv_data pointer. So check if drv_data is valid before overwriting it.
    Added Reference kernel.org https://git.kernel.org/stable/c/cc1a1dcb411fe224f48553cfdcdfe6e61395b69c [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/5e5b85ea0f4bc484bfe4cc73ead51fa48d2366a0 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/995ee1e84e8db7fa5dcdde7dfe0bd7bb6f9bbb8c [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/f0ef883cae309bc5e8cdfcdbc1b4822732ce20a8 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/3565684309e54fa998ea27f37028d67cc3e1dff2 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/1143bfb9b055897975aeaea254da148e19524493 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/f1a1bc8775b26345aba2be278118999e7f661d3d [No types assigned]
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.