Kernel crash via QT1010 terminal-entry BUG_ON
Published Dec 30, 2025 · Updated Dec 30, 2025
Kernel DoS in the QT1010 tuner driver in Linux 4.2 through 6.5.4 allows local users to crash the host during tuner initialization. In qt1010_init, a terminal QT1010_M1 table entry reaches BUG_ON rather than returning an I/O error before the code accesses the following i2c_data element. The shipped table ends with a write operation, and public sources do not identify an attacker-controlled method for placing QT1010_M1 in the terminal slot.
Summary
What happened
Kernel DoS in the QT1010 tuner driver in Linux 4.2 through 6.5.4 allows local users to crash the host during tuner initialization. In qt1010_init, a terminal QT1010_M1 table entry reaches BUG_ON rather than returning an I/O error before the code accesses the following i2c_data element. The shipped table ends with a write operation, and public sources do not identify an attacker-controlled method for placing QT1010_M1 in the terminal slot.
The record
- CVE
- CVE-2023-54282
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- 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 <1a6bf53fffe0b7ebe2a0f402b44f14f90cffd164
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <257092cb544c7843376b3e161f789e666ef06c98
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2ae53dd15eef90d34fc084b5b2305a67bb675a26
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <48bb6a9fa5cb150ac2a22b3c779c96bc0ed21071
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <641e60223971e95472a2a9646b1e7f94d441de45
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6cae780862d221106626b2b5fb21a197f398c6ec
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee630b29ea44d1851bb6c903f400956604834463
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f844bc3a47d8d1c55a4a9cfca38c538e9df7e678
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