LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42141: Bluetooth: ISO: Check socket flag instead of hcon

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: Check socket flag instead of hcon This fixes the following Smatch static checker warning: net/bluetooth/iso.c:1364 iso_sock_recvmsg() error: we previously assumed 'pi->conn->hcon' could be null (line 1359) net/bluetooth/iso.c 1347 static int iso_sock_recvmsg(struct socket *sock, struct msghdr *msg, 1348 size_t len, int flags) 1349 { 1350 struct sock *sk = sock->sk; 1351 struct iso_pinfo *pi = iso_pi(sk); 1352 1353 BT_DBG("sk %p", sk); 1354 1355 if (test_and_clear_bit(BT_SK_DEFER_SETUP, &bt_sk(sk)->flags)) { 1356 lock_sock(sk); 1357 switch (sk->sk_state) { 1358 case BT_CONNECT2: 1359 if (pi->conn->hcon && ^^^^^^^^^^^^^^ If ->hcon is NULL 1360 test_bit(HCI_CONN_PA_SYNC, &pi->conn->hcon->flags)) { 1361 iso_conn_big_sync(sk); 1362 sk->sk_state = BT_LISTEN; 1363 } else { --> 1364 iso_conn_defer_accept(pi->conn->hcon); ^^^^^^^^^^^^^^ then we're toast 1365 sk->sk_state = BT_CONFIG; 1366 } 1367 release_sock(sk); 1368 return 0; 1369 case BT_CONNECTED: 1370 if (test_bit(BT_SK_PA_SYNC,

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel Bluetooth ISO bug where the kernel could dereference a missing connection object. The public record does not provide CVSS, CWE, confirmed impact, or active exploitation. Treat it as a kernel reliability and hardening issue, especially for systems using Bluetooth features.

Executive priority

Prioritize normal kernel patch management rather than emergency response, unless Bluetooth is widely enabled on sensitive endpoints. Escalate if your distribution rates the issue higher or confirms broader impact.

Technical view

The issue is in net/bluetooth/iso.c, iso_sock_recvmsg(). A path checked pi->conn->hcon for one branch but later passed pi->conn->hcon to iso_conn_defer_accept() without ensuring it was non-null. Stable kernel commits change the logic to use socket state/flags instead.

Likely exposure

Exposure is limited to Linux systems with affected kernel versions and relevant Bluetooth ISO code reachable. The source bundle lists Linux kernel 6.6-era affected data and stable fix references, but exact exposure depends on distribution backports and whether Bluetooth is enabled or used.

Exploitation context

No KEV listing is present, and the provided sources do not report active exploitation or a public exploit. The available evidence supports a kernel null-pointer handling flaw found by static analysis, not a confirmed real-world attack chain.

Researcher notes

The record lacks CVSS, CWE, attacker prerequisites, and impact detail. Analysis should stay anchored to the ISO receive/deferred setup null hcon path and the stable commits. Avoid assuming privilege escalation, remote code execution, or exploitability without additional vendor evidence.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Check Linux distribution advisories for backported fixed kernel packages.
  • Prioritize systems where Bluetooth is enabled or business-critical.
  • If Bluetooth is unnecessary, follow vendor guidance to disable or restrict it.

Validation and detection

  • Inventory Linux kernel versions across laptops, servers, appliances, and embedded systems.
  • Map installed kernels to distribution advisories and the referenced stable commits.
  • Confirm Bluetooth status and business need on exposed endpoints.
  • Verify patched kernels are running after reboot, not only installed.
Prepared
Confidence
medium
Sources
5

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-42141 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
2ADP providers
4Source links

SSVC decision data

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

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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfbdc4bc47268953c80853489f696e02d61f9a2c6, fbdc4bc47268953c80853489f696e02d61f9a2c6, fbdc4bc47268953c80853489f696e02d61f9a2c6, c03a10bd5b6ccb22921e04bcddc987410df7e7a9, 6.5.12unaffected
LinuxLinux6.6, 0, 6.6.39, 6.9.9, 6.10affected
Weakness

CWE details

No CWE listed

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