Kernel crash via zero-length I2C message
Published May 14, 2025 · Updated May 11, 2026
NULL pointer dereference in affected Linux kernel versions starting at 2.6.27 allows local users to crash the system via an I2C message. The dw2102_i2c_transfer function accepts a user-controlled message with a null buffer when its length is zero, then reads msg[i].buf[0] without validating that a byte exists. Triggering the path requires local access to a system using the dw2102 driver with supported DVB USB hardware; the bounded consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in affected Linux kernel versions starting at 2.6.27 allows local users to crash the system via an I2C message. The dw2102_i2c_transfer function accepts a user-controlled message with a null buffer when its length is zero, then reads msg[i].buf[0] without validating that a byte exists. Triggering the path requires local access to a system using the dw2102 driver with supported DVB USB hardware; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2023-53146
- Published
- May 14, 2025
- 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
- May 14, 2025CVE 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=2.6.27
- Affected versionversion=7fd4828f6cc5bd4339ff58e372ccb5f528548b30 <08dfcbd03b2b7f918c4f87c6ff637054e510df74
- Affected versionversion=7fd4828f6cc5bd4339ff58e372ccb5f528548b30 <5ae544d94abc8ff77b1b9bf8774def3fa5689b5b
- Affected versionversion=7fd4828f6cc5bd4339ff58e372ccb5f528548b30 <77cbd42d29de9ffc93d5529bab8813cde53af14c
- Affected versionversion=7fd4828f6cc5bd4339ff58e372ccb5f528548b30 <903566208ae6bb9c0e7e54355ce75bf6cf72485d
- Affected versionversion=7fd4828f6cc5bd4339ff58e372ccb5f528548b30 <97fdbdb750342cbc204befde976872fedb406ee6
- Affected versionversion=7fd4828f6cc5bd4339ff58e372ccb5f528548b30 <beb9550494e7349f92b9eaa283256a5ad9b1c9be
- Affected versionversion=7fd4828f6cc5bd4339ff58e372ccb5f528548b30 <ecbe6d011b95c7da59f014f8d26cb7245ed1e11e
- Affected versionversion=7fd4828f6cc5bd4339ff58e372ccb5f528548b30 <fb28afab113a82b89ffec48c8155ec05b4f8cb5e
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