CVE-2025-68305
BaseFortify
Publication date: 2025-12-16
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved by synchronizing the socket write iter and sock bind operations using hci_dev_lock to prevent the race condition. Immediate mitigation would involve updating the Linux kernel to a version that includes this fix.
Can you explain this vulnerability to me?
This vulnerability is a race condition in the Linux kernel's Bluetooth subsystem, specifically in the hci_sock component. It occurs between the socket bind operation and the socket write iterator, where the bind operation may free a command object just before the write iterator tries to send it. This leads to a use-after-free (UAF) condition, which can cause memory corruption or crashes. The fix involves using a lock (hci_dev_lock) to synchronize these operations and prevent the race.
How can this vulnerability impact me? :
The vulnerability can lead to use-after-free memory errors in the Bluetooth subsystem of the Linux kernel. This can cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or cause denial of service by exploiting the race condition.