Local kernel crash via unchecked work cancellation
Published Dec 30, 2025 · Updated Dec 30, 2025
NULL pointer dereference in affected Linux kernel releases allows local users to crash the system during Bluetooth SDIO device removal. The btsdio_remove function calls cancel_work_sync on data->work before checking whether the driver-data pointer is NULL. Reachability requires local low-privileged access and the Bluetooth SDIO removal path; the documented consequence is a kernel crash only.
Summary
What happened
NULL pointer dereference in affected Linux kernel releases allows local users to crash the system during Bluetooth SDIO device removal. The btsdio_remove function calls cancel_work_sync on data->work before checking whether the driver-data pointer is NULL. Reachability requires local low-privileged access and the Bluetooth SDIO removal path; the documented consequence is a kernel crash only.
The record
- CVE
- CVE-2023-54197
- 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=1e9ac114c4428fdb7ff4635b45d4f46017e8916f <d8d7ce037d9a8f1f0714ece268c4c2c50845bbc3
- Affected versionversion=1e9ac114c4428fdb7ff4635b45d4f46017e8916f <db2bf510bd5d57f064d9e1db395ed86a08320c54
- Affected versionversion=6.3
- Affected versionversion=8efae2112d910d8e5166dd0a836791b08721eef1 <a789192f366147a0fbb395650079906d1d04e0b9
- Affected versionversion=95eacef5692545f199fae4e52abfbfa273acb351 <3b4ed52009723f7dfca7a8ca95163bfb441bfb76
- Affected versionversion=a18fb433ceb56e0787546a9d77056dd0f215e762 <de0ffb5145c9f418ad76f00e58d4b91c680410b2
- Affected versionversion=af4d48754d5517d33bac5e504ff1f1de0808e29e <70a104588e3131415e559c06deb834ce259a285a
- Affected versionversion=c59c65a14e8f7d738429648833f3bb3f9df0513f <8f83fa62614c282dd5d1211a0dd99c6a0a515b81
- Affected versionversion=cbf8deacb7053ce3e3fed64b277c6c6989e65bba <952030c914b5f2288609efe868537afcff7a3f51
- Affected versionversion=da3d3fdfb4d523c5da30e35a8dd90e04f0fd8962 <0837d10f6c37a47a0c73bccf1e39513613a2fcc2
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