Kernel crash via uninitialized CCI completion
Published Jul 1, 2026 · Updated Jul 1, 2026
NULL pointer dereference in the Qualcomm CCI I2C driver in affected Linux Kernel releases allows local users to crash the kernel. During cci_remove(), the driver calls cci_halt() for both controller masters even when only one master's completion object was initialized. The condition requires a Qualcomm CCI board with only one master initialized and local access capable of unbinding the device or removing the module; the resulting kernel oops interrupts the system.
Summary
What happened
NULL pointer dereference in the Qualcomm CCI I2C driver in affected Linux Kernel releases allows local users to crash the kernel. During cci_remove(), the driver calls cci_halt() for both controller masters even when only one master's completion object was initialized. The condition requires a Qualcomm CCI board with only one master initialized and local access capable of unbinding the device or removing the module; the resulting kernel oops interrupts the system.
The record
- CVE
- CVE-2026-53339
- Published
- Jul 1, 2026
- Updated
- Jul 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 1, 2026CVE publishedPublication date reported by the CVE source.
- Jul 1, 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.8
- Affected versionversion=e517526195de400158e05a08764d1fb61d579105 <4cd206c1d57a9370d5219f7b1fc45169d7bdf951
- Affected versionversion=e517526195de400158e05a08764d1fb61d579105 <4d2b4a9cda6837e5ee1de1290f2e773a713b71e9
- Affected versionversion=e517526195de400158e05a08764d1fb61d579105 <7107627b8b35015027201e7a095a3f6e30b4a46f
- Affected versionversion=e517526195de400158e05a08764d1fb61d579105 <729ac5a4b966aac42e08a94dea966f4429008548
- Affected versionversion=e517526195de400158e05a08764d1fb61d579105 <8ce7ff721a5e9d06d53ef65d01c89fce6d26d6ff
- Affected versionversion=e517526195de400158e05a08764d1fb61d579105 <a162a260c8c4db7501c65220e76913e8e351f823
- Affected versionversion=e517526195de400158e05a08764d1fb61d579105 <a50b8adb9cdb9a495b0b45583956897b7411ed7a
- Affected versionversion=e517526195de400158e05a08764d1fb61d579105 <e8669d12da0ade52adfe0abe96cd99e708abc9bd
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.
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