# Bluetooth: btusb: Fix potential NULL dereference on kmalloc failure

CVE record · `CVE-2025-38641`

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

Published by the CVE Program (CNA: Linux) at 22 Aug 2025, 16:00 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: `7d70989fcea7f79afe018a7e34d3486406c7a94e to before 5029d80bfc30b60ff57c70ccb04e027acb404f6a` (git)
  - affected: `7d70989fcea7f79afe018a7e34d3486406c7a94e to before b505902c66a282dcb01bcdc015aa1fdfaaa075db` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.16`
  - unaffected: `before 6.16` (semver)
  - unaffected: `6.16.1 to 6.16.*, inclusive` (semver)
  - unaffected: `6.17 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

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

> The Linux kernel's Bluetooth btusb driver has a potential NULL pointer dereference when a kmalloc memory allocation fails. Version 6.16 is affected, and the source gives few details on what an attacker would need or what they could do. Upgrade to Linux 6.16.1 or later within the 6.16 series, or to 6.17 or later.

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.0015, the 4th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 22 Aug 2025, 16:00 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-38641)
- 22 Aug 2025, 16:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-38641)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/5029d80bfc30b60ff57c70ccb04e027acb404f6a>
- <https://git.kernel.org/stable/c/b505902c66a282dcb01bcdc015aa1fdfaaa075db>

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

---

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