CVE-2023-53386Published Sep 18, 2025 · Sep 18Updated Oct 28
Bluetooth: Fix potential use-after-free when clear keys
Linux
High7.8Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d7d41682efc25d58b5bd8b80e85e3c9ce586635c · < 3673952cf0c6cf81b06c66a0b788abeeb02ff3ae| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: Fix potential use-after-free when clear keys
Similar to commit c5d2b6fa26b5 ("Bluetooth: Fix use-after-free in hci_remove_ltk/hci_remove_irk"). We can not access k after kfree_rcu() call.
From the CVE record · Linux
The Linux kernel's Bluetooth code can access a key after it has been scheduled for freeing while clearing keys, causing a potential use-after-free. The input does not specify what an attacker could do or whether exploitation requires network access, authentication, or user interaction.
Anyone running the Linux kernel should check whether their version is affected; affected versions are not specified.