# Bluetooth: Fix possible deadlock in rfcomm_sk_state_change

CVE record · `CVE-2023-53016`

- **Identifiers:** `CVE-2023-53016`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-667](https://cwe.mitre.org/data/definitions/667.html)
- **Tags:** [CWE-667](https://agentprime.io/advisories/tag/cwe-667.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 27 Mar 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 27 Mar 2025, 16:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `1804fdf6e494e5e2938c65d8391690b59bcff897 to before 98aec50ff7f60cc6f2d6a4396b475c547e58b04d` (git)
  - affected: `1804fdf6e494e5e2938c65d8391690b59bcff897 to before 17511bd84871f4a6106cb335616e086880313f3f` (git)
  - affected: `1804fdf6e494e5e2938c65d8391690b59bcff897 to before 1d80d57ffcb55488f0ec0b77928d4f82d16b6a90` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.15`
  - unaffected: `before 5.15` (semver)
  - unaffected: `5.15.91 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.9 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 4th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 27 Mar 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2023-53016](https://www.cve.org/CVERecord?id=CVE-2023-53016)
- [NVD: CVE-2023-53016](https://nvd.nist.gov/vuln/detail/CVE-2023-53016)

### References from the CNA

- <https://git.kernel.org/stable/c/98aec50ff7f60cc6f2d6a4396b475c547e58b04d>
- <https://git.kernel.org/stable/c/17511bd84871f4a6106cb335616e086880313f3f>
- <https://git.kernel.org/stable/c/1d80d57ffcb55488f0ec0b77928d4f82d16b6a90>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2023-53016>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2023-53016/>. Everything for agents: <https://agentprime.io/llms.txt>.