CVE-2023-53673
BaseFortify
Publication date: 2025-10-07
Last updated on: 2026-04-23
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | 6.5 |
| linux | linux_kernel | From 5.16 (inc) to 6.1.42 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.4.7 (exc) |
| linux | linux_kernel | From 5.7 (inc) to 5.15.200 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's Bluetooth subsystem involves improper handling of connection disconnections. Specifically, the disconnect callback is not called before deleting a connection, which can lead to use-after-free errors. This happens because ISO, L2CAP, and SCO connections reference the connection without properly increasing its reference count, so if the disconnect confirmation callback is not called, these connections try to access freed memory, causing kernel crashes or undefined behavior.
How can this vulnerability impact me? :
This vulnerability can cause kernel crashes or instability due to use-after-free errors in the Bluetooth stack. This can lead to denial of service on affected systems, potentially disrupting Bluetooth communications and affecting system reliability.