# Bluetooth: Disable SCO support if READ_VOICE_SETTING is unsupported/broken

CVE record · `CVE-2025-38099`

- **Identifiers:** `CVE-2025-38099`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 3 Jul 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 3 Jul 2025, 08:13 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: `035e1bffc063399ad1e193f6e4d8f70bb2f6301f to before f48ee562c095e552a30b8d9cc0566a267b410f8a` (git)
  - affected: `a256de0d34e5937da8e9e0b23a8fa17ec32afa7d to before ec1f015ec0c6fd250a6564e8452f7bb3160b9cb1` (git)
  - affected: `ff26b2dd6568392f60fa67a4e58279938025c3af to before 14d17c78a4b1660c443bae9d38c814edea506f62` (git)
  - affected: `ddb89022bb79e04ee47d830788cc1d20751520d0` (git)
  - affected: `6.13.12 to before 6.14` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.12.24 to before 6.12.31` (semver)
  - affected: `6.14.2 to before 6.14.9` (semver)
  - Other versions: unaffected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel Bluetooth stack is affected in several version ranges, including commits from before the fixes and releases 6.12.24 through 6.12.31 and 6.14.2 through 6.14.9. The source gives few details on who can trigger the issue or how. It says a SCO connection made without the proper voice setting can cause the Bluetooth controller to lock up. Upgrade to a fixed kernel version, such as 6.12.31 or 6.14.9 or later on those branches. No other workaround is listed.

Written 16 Nov 2026.

## 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

No source has published a CVSS score for this record yet.

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

## Timeline

- 3 Jul 2025, 08:13 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-38099)
- 3 Jul 2025, 09:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-38099)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/f48ee562c095e552a30b8d9cc0566a267b410f8a>
- <https://git.kernel.org/stable/c/ec1f015ec0c6fd250a6564e8452f7bb3160b9cb1>
- <https://git.kernel.org/stable/c/14d17c78a4b1660c443bae9d38c814edea506f62>

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-2025-38099>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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