Answer in brief
CVE-2023-52871 records a High severity (CVSS 7.1) vulnerability in soc: qcom: llcc: Handle a second device without data corruption. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-52871 records a High severity (CVSS 7.1) vulnerability in soc: qcom: llcc: Handle a second device without data corruption. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <cc1a1dcb411fe224f48553cfdcdfe6e61395b69c || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <5e5b85ea0f4bc484bfe4cc73ead51fa48d2366a0 || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <995ee1e84e8db7fa5dcdde7dfe0bd7bb6f9bbb8c || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <f0ef883cae309bc5e8cdfcdbc1b4822732ce20a8 || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <3565684309e54fa998ea27f37028d67cc3e1dff2 || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <1143bfb9b055897975aeaea254da148e19524493 || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <f1a1bc8775b26345aba2be278118999e7f661d3d | cc1a1dcb411fe224f48553cfdcdfe6e61395b69c, 5e5b85ea0f4bc484bfe4cc73ead51fa48d2366a0, 995ee1e84e8db7fa5dcdde7dfe0bd7bb6f9bbb8c, f0ef883cae309bc5e8cdfcdbc1b4822732ce20a8, 3565684309e54fa998ea27f37028d67cc3e1dff2, 1143bfb9b055897975aeaea254da148e19524493, f1a1bc8775b26345aba2be278118999e7f661d3d |
| Linux/Linuxgeneric | 4.19 | Not reported |
Published upstream
May 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <cc1a1dcb411fe224f48553cfdcdfe6e61395b69c || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <5e5b85ea0f4bc484bfe4cc73ead51fa48d2366a0 || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <995ee1e84e8db7fa5dcdde7dfe0bd7bb6f9bbb8c || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <f0ef883cae309bc5e8cdfcdbc1b4822732ce20a8 || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <3565684309e54fa998ea27f37028d67cc3e1dff2 || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <1143bfb9b055897975aeaea254da148e19524493 || >=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <f1a1bc8775b26345aba2be278118999e7f661d3d | cc1a1dcb411fe224f48553cfdcdfe6e61395b69c, 5e5b85ea0f4bc484bfe4cc73ead51fa48d2366a0, 995ee1e84e8db7fa5dcdde7dfe0bd7bb6f9bbb8c, f0ef883cae309bc5e8cdfcdbc1b4822732ce20a8, 3565684309e54fa998ea27f37028d67cc3e1dff2, 1143bfb9b055897975aeaea254da148e19524493, f1a1bc8775b26345aba2be278118999e7f661d3d |
| Linux/Linuxgeneric | 4.19 | Not reported |
Published upstream
May 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.