LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38620: Bluetooth: HCI: Remove HCI_AMP support

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: HCI: Remove HCI_AMP support Since BT_HS has been remove HCI_AMP controllers no longer has any use so remove it along with the capability of creating AMP controllers. Since we no longer need to differentiate between AMP and Primary controllers, as only HCI_PRIMARY is left, this also remove hdev->dev_type altogether.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-38620 is a Linux kernel Bluetooth issue addressed by removing obsolete HCI_AMP controller support. The public record does not describe business impact, attacker requirements, or severity. Treat this as kernel maintenance risk: prioritize systems with Bluetooth enabled or exposed, but avoid emergency language without stronger exploitation evidence.

Executive priority

Handle through scheduled kernel patching unless local exposure is high. The lack of severity, impact, and exploitation evidence argues against emergency response, but Bluetooth-capable Linux fleets should not leave obsolete kernel code untracked.

Technical view

The fix removes HCI_AMP support from Linux Bluetooth HCI because BT_HS was already removed, leaving only HCI_PRIMARY controllers. The CVE record lists Linux kernel versions and stable commits, but provides no CVSS, CWE, impact class, or exploit preconditions.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or branches before the referenced stable fixes, especially where Bluetooth support is enabled. The source bundle does not identify affected distributions, hardware requirements, or whether default configurations are vulnerable.

Exploitation context

CISA KEV status is false, and the provided sources do not report active exploitation. The public description does not provide attack path, privilege requirements, or impact details, so exploitation likelihood cannot be reliably assessed from this bundle alone.

Researcher notes

The source record is sparse and appears change-driven: removing unused AMP controller support after BT_HS removal. Researchers should review the linked kernel commits and branch history to determine the actual vulnerable behavior and whether distribution backports differ.

Mitigation direction

  • Apply vendor Linux kernel updates that include the referenced stable fixes.
  • Check distribution advisories for affected package versions and supported upgrade paths.
  • Prioritize hosts with Bluetooth enabled, mobile endpoints, and edge devices.
  • If Bluetooth is unnecessary, follow vendor guidance to disable or restrict it.
  • Track kernel update completion through normal vulnerability management workflows.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and appliances.
  • Confirm installed kernels include the relevant stable commit for their branch.
  • Review vendor advisories for distribution-specific fixed package versions.
  • Verify Bluetooth-enabled systems are included in remediation scope.
  • Document exceptions where kernel updates depend on vendor support windows.
Prepared
Confidence
medium
Sources
6

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-38620 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
5Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux244bc377591c3882f454882357bc730c90cbedb5, 244bc377591c3882f454882357bc730c90cbedb5, 244bc377591c3882f454882357bc730c90cbedb5, 244bc377591c3882f454882357bc730c90cbedb5unaffected
LinuxLinux4.3, 0, 6.6.33, 6.8.12, 6.9.3, 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.