LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26886: Bluetooth: af_bluetooth: Fix deadlock

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: af_bluetooth: Fix deadlock Attemting to do sock_lock on .recvmsg may cause a deadlock as shown bellow, so instead of using sock_sock this uses sk_receive_queue.lock on bt_sock_ioctl to avoid the UAF: INFO: task kworker/u9:1:121 blocked for more than 30 seconds. Not tainted 6.7.6-lemon #183 Workqueue: hci0 hci_rx_work Call Trace: <TASK> __schedule+0x37d/0xa00 schedule+0x32/0xe0 __lock_sock+0x68/0xa0 ? __pfx_autoremove_wake_function+0x10/0x10 lock_sock_nested+0x43/0x50 l2cap_sock_recv_cb+0x21/0xa0 l2cap_recv_frame+0x55b/0x30a0 ? psi_task_switch+0xeb/0x270 ? finish_task_switch.isra.0+0x93/0x2a0 hci_rx_work+0x33a/0x3f0 process_one_work+0x13a/0x2f0 worker_thread+0x2f0/0x410 ? __pfx_worker_thread+0x10/0x10 kthread+0xe0/0x110 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK>

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-26886 is a Linux kernel Bluetooth flaw that can deadlock Bluetooth receive processing. The direct business risk is service disruption on systems using affected kernels with Bluetooth exposed locally or nearby. The sources do not show data theft, privilege escalation, or confirmed active exploitation.

Executive priority

Treat this as a moderate operational risk. It is not shown to enable data compromise, but nearby unauthenticated attackers may affect availability on Bluetooth-enabled Linux devices. Patch through normal kernel update channels, with priority for mobile, physical-accessible, and operationally sensitive devices.

Technical view

The issue is in Linux Bluetooth af_bluetooth locking during recvmsg and bt_sock_ioctl. Taking sock_lock in the receive path can deadlock; the kernel fix uses sk_receive_queue.lock instead to avoid the use-after-free risk. CVSS 3.1 is 6.5 with adjacent network access and high availability impact.

Likely exposure

Exposure is most likely on Linux systems running affected kernel builds with Bluetooth enabled and reachable by a nearby attacker. Servers without Bluetooth hardware or with Bluetooth disabled have materially lower practical exposure. Exact affected status should be verified against distro kernel backports and the referenced stable commits.

Exploitation context

The CVE record does not identify public exploitation or KEV listing. The attack vector is adjacent network, with no privileges or user interaction required. The documented impact is availability: a blocked Bluetooth worker path can degrade or disrupt Bluetooth functionality or affected kernel processing.

Researcher notes

The source bundle is limited to the CVE description, CVSS vector, affected Linux kernel entries, and upstream stable commit references. It does not provide proof-of-concept details, distribution-specific package names, or evidence of exploitation in the wild.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable Bluetooth locking fix.
  • If Bluetooth is unnecessary, disable Bluetooth adapters or services on affected systems.
  • Prioritize laptops, kiosks, edge devices, and IoT systems with Bluetooth enabled.
  • Check Linux distribution advisories for backported fixes matching your kernel package.
  • Avoid direct wrangler or unrelated deployment actions; this is an OS patching issue.

Validation and detection

  • Inventory Linux kernel versions and Bluetooth hardware across managed assets.
  • Confirm whether Bluetooth services or adapters are enabled on each exposed device.
  • Map kernel builds to vendor advisories or the referenced stable commits.
  • Review system logs for Bluetooth worker stalls, deadlock reports, or availability symptoms.
  • Track remediation through kernel package version, not only upstream version strings.
Prepared
Confidence
medium
Sources
8

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.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-26886 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
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2024-26886Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2b16d960c79abc397f102c3d23d30005b68cb036, 1d576c3a5af850bf11fbd103f9ba11aa6d6061fb, 2e07e8348ea454615e268222ae3fc240421be768, 2e07e8348ea454615e268222ae3fc240421be768, 2e07e8348ea454615e268222ae3fc240421be768, db1b14eec8c61a20374de9f9c2ddc6c9406a8c42, 37f71e2c9f515834841826f4eb68ec33cfb2a1ff, 5.15.146, 6.6.9, 5.10.206, 6.1.70unaffected
LinuxLinux6.7, 0, 5.15.209, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.