LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42133: Bluetooth: Ignore too large handle values in BIG

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Ignore too large handle values in BIG hci_le_big_sync_established_evt is necessary to filter out cases where the handle value is belonging to ida id range, otherwise ida will be erroneously released in hci_conn_cleanup.

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 flaw in BIG synchronization handling. The kernel could mishandle an oversized Bluetooth handle and release the wrong internal identifier during connection cleanup. Business urgency depends on whether affected Linux systems have Bluetooth enabled and whether vendor kernels include the stable fixes.

Executive priority

Treat this as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize patch validation for Linux endpoints or devices using Bluetooth, and fold remediation into the next kernel update cycle unless vendor guidance raises severity.

Technical view

The fix changes Bluetooth handling around hci_le_big_sync_established_evt so handle values outside the expected BIG range are ignored. Without that filter, hci_conn_cleanup can erroneously release an ida-managed identifier. The source bundle does not provide CVSS, CWE, crash impact detail, privilege requirements, or exploitability evidence.

Likely exposure

Exposure is limited to Linux systems running affected kernel builds with relevant Bluetooth functionality present. The bundle lists Linux kernel versions and stable commits, but distro backports may change exposure. Confirm against each vendor kernel package rather than relying only on upstream version numbers.

Exploitation context

No active exploitation is supported by the provided sources. The CVE is not listed as KEV in the bundle, and no cited source describes public exploitation, exploit code, or weaponized use.

Researcher notes

Evidence is thin: upstream describes the bug and fix, but not impact class, attacker position, or reproducibility. Focus analysis on the Bluetooth BIG path, handle-range validation, and ida cleanup behavior. Avoid assuming remote code execution, denial of service, or privilege escalation without additional vendor evidence.

Mitigation direction

  • Update to a vendor kernel package containing the referenced stable fixes.
  • Check Linux distribution advisories for CVE-2024-42133 applicability and fixed package versions.
  • Prioritize systems where Bluetooth is enabled, exposed, or operationally required.
  • Track kernel backport status by CVE ID or referenced stable commit IDs.

Validation and detection

  • Inventory Linux kernel versions across servers, desktops, appliances, and embedded systems.
  • Confirm whether Bluetooth support is enabled or present on affected assets.
  • Check installed kernel changelogs for CVE-2024-42133 or referenced commit IDs.
  • Verify vendor advisories before declaring backported kernels unaffected.
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-42133 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
LinuxLinux84cb0143fb8a03bf941c7aaedd56c938c99dafad, 181a42edddf51d5d9697ecdf365d72ebeab5afb0, 181a42edddf51d5d9697ecdf365d72ebeab5afb0, e9f708beada55426c8d678e2f46af659eb5bf4f0, 6.6.2, 6.5.12unaffected
LinuxLinux6.7, 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.