Kernel driver-state corruption via second LLCC probe
Published May 21, 2024 · Updated Aug 5, 2026
Data corruption in the Qualcomm LLCC driver in Linux allows local users to corrupt kernel driver state when a second LLCC device probes. The llcc_probe path assigns per-device state to the global drv_data pointer before confirming that the pointer is unset, so even a failed second probe replaces the first device's state. Reachability requires a Qualcomm platform with a second LLCC device, and consequences beyond kernel driver-state corruption are not publicly documented.
Summary
What happened
Data corruption in the Qualcomm LLCC driver in Linux allows local users to corrupt kernel driver state when a second LLCC device probes. The llcc_probe path assigns per-device state to the global drv_data pointer before confirming that the pointer is unset, so even a failed second probe replaces the first device's state. Reachability requires a Qualcomm platform with a second LLCC device, and consequences beyond kernel driver-state corruption are not publicly documented.
The record
- CVE
- CVE-2023-52871
- Published
- May 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.19
- Affected versionversion=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <1143bfb9b055897975aeaea254da148e19524493
- Affected versionversion=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <3565684309e54fa998ea27f37028d67cc3e1dff2
- Affected versionversion=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <5e5b85ea0f4bc484bfe4cc73ead51fa48d2366a0
- Affected versionversion=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <995ee1e84e8db7fa5dcdde7dfe0bd7bb6f9bbb8c
- Affected versionversion=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <cc1a1dcb411fe224f48553cfdcdfe6e61395b69c
- Affected versionversion=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <f0ef883cae309bc5e8cdfcdbc1b4822732ce20a8
- Affected versionversion=a3134fb09e0bc5bee76e13bf863173b86f21cf87 <f1a1bc8775b26345aba2be278118999e7f661d3d
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo