CVE-2023-52871
soc: qcom: llcc: Handle a second device without data corruption
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.19
References 7
git.kernel.org
- stable/c/cc1a1dcb411fe224f48553cfdcdfe6e61395b69c
- stable/c/5e5b85ea0f4bc484bfe4cc73ead51fa48d2366a0
- stable/c/995ee1e84e8db7fa5dcdde7dfe0bd7bb6f9bbb8c
- stable/c/f0ef883cae309bc5e8cdfcdbc1b4822732ce20a8
- stable/c/3565684309e54fa998ea27f37028d67cc3e1dff2
- stable/c/1143bfb9b055897975aeaea254da148e19524493
- stable/c/f1a1bc8775b26345aba2be278118999e7f661d3d