# CVE-2023-51779: Use after free in n/a

> A race condition in the Linux kernel Bluetooth subsystem allows attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Dec 2023
- **Updated:** 29 Aug 2024
- **Also known as:** AZL-35478, BELL-CVE-2023-51779, DEBIAN-CVE-2023-51779, GHSA-w3hv-rwgr-crx3, SUSE-SU-2024:1025-1, SUSE-SU-2024:1028-1, SUSE-SU-2024:1153-1, UBUNTU-CVE-2023-51779

## What is CVE-2023-51779?

CVE-2023-51779 is a high-severity use after free vulnerability in n/a, published on 25 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

bt_sock_recvmsg in net/bluetooth/af_bluetooth.c in the Linux kernel through 6.6.8 has a use-after-free because of a bt_sock_ioctl race condition.

Weakness: CWE-416 (Use After Free)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kgraft-patch-SLE12-SP5_Update_40` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 13-2.3 |
| `kgraft-patch-SLE12-SP5_Update_47` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 7-2.2 |
| `kgraft-patch-SLE12-SP5_Update_48` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 6-2.2 |

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

Apply the vendor's patch.

## Is CVE-2023-51779 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-51779 is a high-severity use after free vulnerability in n/a, published on 25 Dec 2023. 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-2023-51779 in the wild and no public exploit code.

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

## Sources

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

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