Menu

Star on GitHub · 3.2k

CVE-2023-53252

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: use RCU for hci_conn_params and iterate safely in hci_sync hci_update_accept_list_sync iterates over hdev->pend_le_c…

Published Sep 15, 2025CWE-416EPSS 0.15%

Overview

CVE-2023-53252 is a high-severity vulnerability. It was published on September 15, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: use RCU for hci_conn_params and iterate safely in hci_sync

hci_update_accept_list_sync iterates over hdev->pend_le_conns and

hdev->pend_le_reports, and waits for controller events in the loop body,

without holding hdev lock.

Meanwhile, these lists and the items may be modified e.g. by

le_scan_cleanup. This can invalidate the list cursor or any other item

in the list, resulting to invalid behavior (eg use-after-free).

Use RCU for the hci_conn_params action lists. Since the loop bodies in

hci_sync block and we cannot use RCU or hdev->lock for the whole loop,

copy list items first and then iterate on the copy. Only the flags field

is written from elsewhere, so READ_ONCE/WRITE_ONCE should guarantee we

read valid values.

Free params everywhere with hci_conn_params_free so the cleanup is

guaranteed to be done properly.

This fixes the following, which can be triggered e.g. by BlueZ new

mgmt-tester case "Add +

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2023-53252?

CVE-2023-53252 is a high-severity vulnerability. It was published on September 15, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2023-53252?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2023-53252?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2023-53252?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2023-53252 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2023

View all