Local system crash via stale smsusb work
Published Aug 3, 2023 · Updated Nov 7, 2025
Use-after-free in the smsusb kernel module in Red Hat Enterprise Linux 8 allows local users to crash the system during Siano USB initialization. A failed smscore_start_device() call frees smsusb_device_t while work queued by smsusb_onresponse() can continue and access it. Triggering the flaw requires a Siano USB device and low-privileged local access; the documented consequence is a kernel panic and service interruption.
Summary
What happened
Use-after-free in the smsusb kernel module in Red Hat Enterprise Linux 8 allows local users to crash the system during Siano USB initialization. A failed smscore_start_device() call frees smsusb_device_t while work queued by smsusb_onresponse() can continue and access it. Triggering the flaw requires a Siano USB device and low-privileged local access; the documented consequence is a kernel panic and service interruption.
The record
- CVE
- CVE-2023-4132
- Published
- Aug 3, 2023
- Updated
- Nov 7, 2025
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 3, 2023CVE publishedPublication date reported by the CVE source.
- Nov 7, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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.
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