# CVE-2023-7356: Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID


- **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
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** BELL-CVE-2023-7356, DEBIAN-CVE-2023-7356, GHSA-9pc6-2xgf-x4rp, UBUNTU-CVE-2023-7356

## What is CVE-2023-7356?

CVE-2023-7356 is a high-severity vulnerability in Linux, published on 21 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID

Copy the content of a Periodic Advertisement Report to BASE only if
the service UUID is Basic Audio Announcement Service UUID.

## Which versions are affected by CVE-2023-7356?


## How do I fix CVE-2023-7356?

Upgrade to a fixed version.

## Is CVE-2023-7356 being exploited?

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

Public exploit code:

- Offline Python detector for CVE-2023-7356 exposure in upstream Linux kernels, with CSV/JSON inventories and auditable reports. (github_poc): https://github.com/mehmet-emir-eroglu/CVE-2023-7356

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7356 and fix it if it is affected.

What it is: CVE-2023-7356 is a high-severity vulnerability in Linux, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2023-7356 in the wild and no public exploit code.

Affected product: 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-2023-7356/ (Markdown: https://insights.sbomify.com/CVE-2023-7356/index.md)
```

## Sources

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

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