Menu

Star on GitHub · 3.2k

CVE-2023-54038

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: return ERR_PTR instead of NULL when there is no link hci_connect_sco currently returns NULL when there is…

Published Dec 24, 2025EPSS 0.18%

Overview

CVE-2023-54038 is a known-severity vulnerability. It was published on December 24, 2025.

Technical description

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

Bluetooth: hci_conn: return ERR_PTR instead of NULL when there is no link

hci_connect_sco currently returns NULL when there is no link (i.e. when

hci_conn_link() returns NULL).

sco_connect() expects an ERR_PTR in case of any error (see line 266 in

sco.c). Thus, hcon set as NULL passes through to sco_conn_add(), which

tries to get hcon->hdev, resulting in dereferencing a NULL pointer as

reported by syzkaller.

The same issue exists for iso_connect_cis() calling hci_connect_cis().

Thus, make hci_connect_sco() and hci_connect_cis() return ERR_PTR

instead of NULL.

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-54038?

CVE-2023-54038 is a known-severity vulnerability. It was published on December 24, 2025.

How severe is CVE-2023-54038?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

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

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-54038?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2023-54038 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.