System crash via HCI command cleanup race
Published Jun 8, 2021 · Updated Aug 3, 2024
Double-free memory corruption in Linux Kernel 3.13 and later allows local users to crash the system through a malicious HCI TTY device. In hci_dev_do_open, hci_rx_work can requeue hci_cmd_work after it was flushed, racing cleanup so hdev->sent_cmd is freed twice. Attaching a crafted HCI TTY device needs no extra privileges; demonstrated impact is kernel memory corruption and a system crash.
Summary
What happened
Double-free memory corruption in Linux Kernel 3.13 and later allows local users to crash the system through a malicious HCI TTY device. In hci_dev_do_open, hci_rx_work can requeue hci_cmd_work after it was flushed, racing cleanup so hdev->sent_cmd is freed twice. Attaching a crafted HCI TTY device needs no extra privileges; demonstrated impact is kernel memory corruption and a system crash.
The record
- CVE
- CVE-2021-3564
- Published
- Jun 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-415, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=All Linux kernel versions starting from 3.13
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
- BlockSec reproduce.zip proof of conceptproof of concept · demonstrated
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