Kernel crash via absent Qualcomm SCM device
Published Nov 19, 2024 · Updated May 11, 2026
NULL-pointer dereference in Qualcomm SCM support in Linux 6.11 allows local users to crash the kernel through affected SCM calls. The __get_convention function tests SC7180 compatibility by dereferencing the global __scm device pointer even when no SCM driver instance exists. Systems must use Qualcomm hardware, lack an SCM device-tree entry, and invoke an affected call; the resulting kernel panic interrupts the host.
Summary
What happened
NULL-pointer dereference in Qualcomm SCM support in Linux 6.11 allows local users to crash the kernel through affected SCM calls. The __get_convention function tests SC7180 compatibility by dereferencing the global __scm device pointer even when no SCM driver instance exists. Systems must use Qualcomm hardware, lack an SCM device-tree entry, and invoke an affected call; the resulting kernel panic interrupts the host.
The record
- CVE
- CVE-2024-53069
- Published
- Nov 19, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 19, 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=449d0d84bcd8246b508d07995326d13c54488b8c <3d36e2b1d803f0d1cc674115d295a8f20ddb9268
- Affected versionversion=449d0d84bcd8246b508d07995326d13c54488b8c <ca61d6836e6f4442a77762e1074d2706a2a6e578
- Affected versionversion=6.11
What conditions does exploitation require?
What is affected?
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