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

> Removal of unused HCI_AMP support in the Linux kernel Bluetooth subsystem to clean up code and remove obsolete controller types.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jun 2024
- **Updated:** 23 Aug 2026
- **Also known as:** AZL-68108, BELL-CVE-2024-38620, DEBIAN-CVE-2024-38620, GHSA-xhv2-gw9c-73rm, ROOT-OS-DEBIAN-11-CVE-2024-38620, ROOT-OS-DEBIAN-12-CVE-2024-38620, UBUNTU-CVE-2024-38620

## What is CVE-2024-38620?

CVE-2024-38620 is a high-severity vulnerability in Linux kernel, published on 20 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2024-38620?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-38620?

Apply the vendor's patch.

## Is CVE-2024-38620 being exploited?

There is no known exploitation of CVE-2024-38620 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-38620 and fix it if it is affected.

What it is: CVE-2024-38620 is a high-severity vulnerability in Linux kernel, published on 20 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38620 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-38620/ (Markdown: https://insights.sbomify.com/CVE-2024-38620/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-38620
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-38620
- OSV: https://osv.dev/vulnerability/CVE-2024-38620

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-38620/
Summaries are generated and may contain mistakes; the official description above is the record.