Vulnerability · Published Aug 9, 2025 · Assigned by Linux

CVE-2024-58238Bluetooth: btnxpuart: Resolve TX timeout error in power save stress test

High 7.1

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.1High
Exploit odds (30 days)0.2%top 93.2% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btnxpuart: Resolve TX timeout error in power save stress test This fixes the tx timeout issue seen while running a stress test on btnxpuart for couple of hours, such that the interval between two HCI commands coincide with the power save timeout value of 2 seconds. Test procedure using bash script: <load btnxpuart.ko> hciconfig hci0 up //Enable Power Save feature hcitool -i hci0 cmd 3f 23 02 00 00 while (true) do hciconfig hci0 leadv sleep 2 hciconfig hci0 noleadv sleep 2 done Error log, after adding few more debug prints: Bluetooth: btnxpuart_queue_skb(): 01 0A 20 01 00 Bluetooth: hci0: Set UART break: on, status=0 Bluetooth: hci0: btnxpuart_tx_wakeup() tx_work scheduled Bluetooth: hci0: btnxpuart_tx_work() dequeue: 01 0A 20 01 00 Can't set advertise mode on hci0: Connection timed out (110) Bluetooth: hci0: command 0x200a tx timeout When the power save mechanism turns on UART break, and btnxpuart_tx_work() is scheduled simultaneously, psdata->ps_state is read as PS_STATE_AWAKE, which prevents the psdata->work from being scheduled, which is responsible to turn OFF UART break. This issue is fixed by adding a ps_lock mutex around UART break on/off as well as around ps_state read/write. btnxpuart_tx_wakeup() will now read updated ps_state value. If ps_state is PS_STATE_SLEEP, it will first schedule psdata->work, and then it will reschedule itself once UART break has been turned off and ps_state is PS_STATE_AWAKE. Tested above script for 50,000 iterations and TX timeout error was not observed anymore.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.9.7-1DEBIAN-CVE-2024-58238
Debian:14linux6.9.7-1DEBIAN-CVE-2024-58238
Ubuntu:24.04:LTSlinux6.8.0-50.51UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-aws6.8.0-1020.22UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1020.22~22.04.1UBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-azure6.8.0-1020.23UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1020.23~22.04.1UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-gcp6.8.0-1019.21UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1019.21~22.04.1UBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-gke6.8.0-1015.19UBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1002.4UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-50.51~22.04.1UBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-ibm6.8.0-1017.17UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1017.17~22.04.1UBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-50.51.1UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-50.51.1~22.04.1UBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1019.21UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1019.21~22.04.1UBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1019.21.1UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-oracle6.8.0-1017.18UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1017.18~22.04.1UBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-raspi6.8.0-1016.18UBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-50.51.1~22.04.1UBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2024-58238
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2024-58238
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1017.18UBUNTU-CVE-2024-58238

Affected products (as reported)

VendorProductVersions
Linux Linux 689ca16e523278470c38832a3010645a78c544d8 – before 9d5df94ce0e213d5b549633f528f96114c736190689ca16e523278470c38832a3010645a78c544d8 – before e4db90e4eb8d5487098712ffb1048f3fa6d25e98
Linux Linux 6.4

References