Local crash via zero-length I2C message
Published Dec 30, 2025 · Updated Dec 30, 2025
Null-pointer dereference in the Linux kernel AF9005 USB DVB driver allows local users to crash affected systems through an I2C message. af9005_i2c_xfer accepts a user-controlled message whose buffer is null and length is zero, then reads msg[i].buf[0] without validating the length. Reachability requires the AF9005 driver path and a crafted local transfer; the documented consequence is a kernel crash.
Summary
What happened
Null-pointer dereference in the Linux kernel AF9005 USB DVB driver allows local users to crash affected systems through an I2C message. af9005_i2c_xfer accepts a user-controlled message whose buffer is null and length is zero, then reads msg[i].buf[0] without validating the length. Reachability requires the AF9005 driver path and a crafted local transfer; the documented consequence is a kernel crash.
The record
- CVE
- CVE-2023-54314
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <033b0c0780adee32dde218179e9bc51d2525108f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0c02eb70b1dd4ae9bb304ce6cdadbc6faba2b2e9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <63d962ac7a52c0ff4cd09af2e284dce5e5955dfe
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <98c12abb275b75a98ff62de9466d21e4daa98536
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <abb6fd93e05e80668d2317fe1110bc99b05034c3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c7e5ac737db25d7387fe517cb5207706782b6cf8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e595ff350b2fd600823ee8491df7df693ae4b7c5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f4ee84f27625ce1fdf41e8483fa0561a1b837d10
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