Kernel crash via non-serdev suspend NULL dereference
Published May 17, 2024 · Updated May 11, 2026
NULL-pointer dereference in affected Linux kernels allows local users to crash the kernel during suspend on configured systems. In drivers/bluetooth/hci_qca.c, the wakeup callback dereferences the HCI UART serdev pointer without checking whether a Qualcomm ROME controller was registered through the Bluetooth line discipline, which leaves that pointer null. The path is limited to that non-serdev controller registration, and reaching it requires local access to initiate system suspend; the resulting impact is a kernel crash.
Summary
What happened
NULL-pointer dereference in affected Linux kernels allows local users to crash the kernel during suspend on configured systems. In drivers/bluetooth/hci_qca.c, the wakeup callback dereferences the HCI UART serdev pointer without checking whether a Qualcomm ROME controller was registered through the Bluetooth line discipline, which leaves that pointer null. The path is limited to that non-serdev controller registration, and reaching it requires local access to initiate system suspend; the resulting impact is a kernel crash.
The record
- CVE
- CVE-2024-35851
- Published
- May 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=5.13
- Affected versionversion=c1a74160eaf1ac218733b371158432b52601beff <52f9041deaca3fc5c40ef3b9cb943993ec7d2489
- Affected versionversion=c1a74160eaf1ac218733b371158432b52601beff <6b47cdeb786c38e4174319218db3fa6d7b4bba88
- Affected versionversion=c1a74160eaf1ac218733b371158432b52601beff <73e87c0a49fda31d7b589edccf4c72e924411371
- Affected versionversion=c1a74160eaf1ac218733b371158432b52601beff <b64092d2f108f0cd1d7fd7e176f5fb2a67a2f189
- Affected versionversion=c1a74160eaf1ac218733b371158432b52601beff <e60502b907be350c518819297b565007a94c706d
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
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