# CVE-2020-27153: Use after free in n/a > A double free in BlueZ allows remote attackers to cause denial of service or execute code during Bluetooth service discovery. - **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Oct 2020 - **Updated:** 15 Apr 2026 - **Also known as:** ALPINE-CVE-2020-27153, ALSA-2021:1598, DEBIAN-CVE-2020-27153, DLA-2410-1, GHSA-hrr3-cwf8-mjp6, MGASA-2020-0419, OESA-2021-1307, RHSA-2021:1598, RLSA-2021:1598, SUSE-SU-2020:3165-1, UBUNTU-CVE-2020-27153, openSUSE-SU-2020:1876-1, openSUSE-SU-2020:1880-1 ## What is CVE-2020-27153? CVE-2020-27153 is a high-severity use after free vulnerability in Debian Debian Linux, published on 15 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description In BlueZ before 5.55, a double free was found in the gatttool disconnect_cb() routine from shared/att.c. A remote attacker could potentially cause a denial of service or code execution, during service discovery, due to a redundant disconnect MGMT event. Weakness: CWE-415 (Double Free) ## Which versions are affected by CVE-2020-27153? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bluez-libs-devel` | AlmaLinux:8 | All versions | 5.52-4.el8.alma | | `bluez-cups` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.52-4.el8 | | `bluez-cups-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.52-4.el8 | | `bluez-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.52-4.el8 | | `bluez-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.52-4.el8 | | `bluez-hid2hci-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.52-4.el8 | | `bluez-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.52-4.el8 | | `bluez-obexd-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.52-4.el8 | | `bluez` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.52-4.el8 | | `bluez-cups-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.52-4.el8 | | `bluez-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.52-4.el8 | | `bluez-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.52-4.el8 | | `bluez-hid2hci` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.52-4.el8 | | `bluez-hid2hci-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.52-4.el8 | | `bluez-libs` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.52-4.el8 | | `bluez-libs-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.52-4.el8 | | `bluez-obexd` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.52-4.el8 | | `bluez-obexd-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.52-4.el8 | | `bluez-cups-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.52-4.el8 | | `bluez-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.52-4.el8 | | `bluez-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.52-4.el8 | | `bluez-hid2hci-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.52-4.el8 | | `bluez-libs-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.52-4.el8 | | `bluez-libs-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.52-4.el8 | | `bluez-obexd-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.52-4.el8 | | `bluez` | Rocky Linux:8 | All versions | 0:5.52-4.el8 | | `bluez` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 5.48-5.28.1 | | `bluez` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP1 | All versions | 5.48-5.28.1 | | `bluez` | SUSE:Linux Enterprise Workstation Extension 15 SP1 | All versions | 5.48-5.28.1 | | `bluez` | openSUSE:Leap 15.1 | All versions | 5.48-lp151.8.15.1 | | `bluez` | openSUSE:Leap 15.2 | All versions | 5.48-lp152.12.6.1 | Products: Bluez Bluez, Debian Debian Linux, Opensuse Leap. ## How do I fix CVE-2020-27153? Upgrade to a fixed version. ## Is CVE-2020-27153 being exploited? There is no known exploitation of CVE-2020-27153 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2021-43400](https://insights.sbomify.com/CVE-2021-43400/): Use after free in n/a (critical 9.1) - [CVE-2024-8805](https://insights.sbomify.com/CVE-2024-8805/): BlueZ HID over GATT Profile Improper Access Control Remote Code Execution Vulnerability (high 8.8) - [CVE-2022-39176](https://insights.sbomify.com/CVE-2022-39176/): Information disclosure in n/a (high 8.8) - [CVE-2022-39177](https://insights.sbomify.com/CVE-2022-39177/): Denial of service in n/a (high 8.8) - [CVE-2022-0204](https://insights.sbomify.com/CVE-2022-0204/): Memory corruption in bluez (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-27153 and fix it if it is affected. What it is: CVE-2020-27153 is a high-severity use after free vulnerability in Debian Debian Linux, published on 15 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-27153 in the wild and no public exploit code. Affected product: Debian Debian Linux. 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-2020-27153/ (Markdown: https://insights.sbomify.com/CVE-2020-27153/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-27153 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-27153 - OSV: https://osv.dev/vulnerability/CVE-2020-27153 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-27153/ Summaries are generated and may contain mistakes; the official description above is the record.