# CVE-2022-0204: Memory corruption in bluez

> A heap overflow in the BlueZ Bluetooth stack allows local network attackers to cause a denial of service via crafted files.

- **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:** 9 Mar 2022
- **Updated:** 15 Apr 2026
- **Also known as:** DEBIAN-CVE-2022-0204, GHSA-479m-xcq5-9g2q, GHSA-g2fr-rq52-c2h3, MGASA-2022-0058, OESA-2022-1595, SUSE-SU-2022:2837-1, SUSE-SU-2022:2883-1, SUSE-SU-2022:3247-1, UBUNTU-CVE-2022-0204, USN-5275-1, openSUSE-SU-2024:12394-1

## What is CVE-2022-0204?

CVE-2022-0204 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 9 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A heap overflow vulnerability was found in bluez in versions prior to 5.63. An attacker with local network access could pass specially crafted files causing an application to halt or crash, leading to a denial of service.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2022-0204?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bluez` | SUSE:Enterprise Storage 6 | All versions | 5.48-150000.5.31.1 |
| `bluez` | SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | All versions | 5.48-150000.5.31.1 |
| `bluez` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 5.48-150000.5.31.1 |
| `bluez` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 5.48-150000.5.31.1 |
| `bluez` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 5.48-150000.5.31.1 |
| `bluez` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 5.55-150300.3.11.1 |
| `bluez` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 5.62-150400.4.5.1 |
| `bluez` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP3 | All versions | 5.55-150300.3.11.1 |
| `bluez` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP4 | All versions | 5.62-150400.4.5.1 |
| `bluez` | SUSE:Linux Enterprise Server 15 SP1-BCL | All versions | 5.48-150000.5.31.1 |
| `bluez` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 5.48-150000.5.31.1 |
| `bluez` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 5.48-150000.5.31.1 |
| `bluez` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 5.48-150000.5.31.1 |
| `bluez` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 5.48-150000.5.31.1 |
| `bluez` | SUSE:Linux Enterprise Workstation Extension 15 SP3 | All versions | 5.55-150300.3.11.1 |
| `bluez` | SUSE:Linux Enterprise Workstation Extension 15 SP4 | All versions | 5.62-150400.4.5.1 |
| `bluez` | openSUSE:Leap 15.3 | All versions | 5.55-150300.3.11.1 |
| `bluez` | openSUSE:Leap 15.4 | All versions | 5.62-150400.4.5.1 |
| `bluez` | openSUSE:Tumbleweed | All versions | 5.65-3.1 |

Products: Bluez Bluez, Debian Debian Linux, Fedoraproject Fedora.

## How do I fix CVE-2022-0204?

Upgrade to a fixed version.

## Is CVE-2022-0204 being exploited?

There is no known exploitation of CVE-2022-0204 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-2019-8922](https://insights.sbomify.com/CVE-2019-8922/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0204 and fix it if it is affected.

What it is: CVE-2022-0204 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 9 Mar 2022. 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-2022-0204 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-2022-0204/ (Markdown: https://insights.sbomify.com/CVE-2022-0204/index.md)
```

## Sources

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

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