LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux Bluetooth driver reliability issue. On systems using the btnxpuart Bluetooth driver with power saving, a timing race can cause Bluetooth commands to time out. The provided sources describe stress-test failure and a kernel fix, not data theft or remote takeover.

Executive priority

Treat as low urgency unless affected Bluetooth functionality is business-critical. The primary demonstrated impact is reliability degradation, not confirmed compromise. Patch through normal kernel maintenance, with earlier action for products or sites depending on this Bluetooth path.

Technical view

The btnxpuart driver can race between UART break power-save handling and TX work scheduling. A stale PS_STATE_AWAKE read can prevent work that clears UART break, causing HCI command TX timeout. The fix adds ps_lock protection around UART break changes and power-save state reads and writes.

Likely exposure

Exposure appears limited to Linux systems using the btnxpuart Bluetooth UART driver, likely for NXP Bluetooth hardware, with affected kernel builds and power-save behavior enabled. Systems without this driver or Bluetooth path are unlikely to be exposed based on the provided sources.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. Evidence describes a reproducible stress-test timing condition over hours, not a public exploit. Security impact beyond Bluetooth command timeout is not established in the supplied material.

Researcher notes

The CVE data lacks CVSS, CWE, and a detailed affected-version matrix in the supplied bundle. Analysis should stay tied to the listed Linux kernel affected records and two stable commits. Do not infer remote exploitability or broader Bluetooth-stack impact from this evidence alone.

Mitigation direction

  • Update to a kernel or vendor package containing the referenced stable fixes.
  • Track Linux distribution advisories for backported fixes matching your kernel branch.
  • Prioritize systems where btnxpuart Bluetooth is enabled and operationally important.
  • If patching is delayed, consult vendor guidance before changing Bluetooth power-save behavior.

Validation and detection

  • Inventory Linux kernels and identify systems using the btnxpuart Bluetooth driver.
  • Check whether installed kernel source or package changelog includes the referenced fix commits.
  • Review Bluetooth reliability logs for HCI command TX timeout symptoms.
  • Confirm patched systems no longer reproduce the documented power-save timeout behavior.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-58238 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux689ca16e523278470c38832a3010645a78c544d8, 689ca16e523278470c38832a3010645a78c544d8unaffected
LinuxLinux6.4, 0, 6.6.49, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.