LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38641: Bluetooth: btusb: Fix potential NULL dereference on kmalloc failure

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: Fix potential NULL dereference on kmalloc failure Avoid potential NULL pointer dereference by checking the return value of kmalloc and handling allocation failure properly.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the Bluetooth USB driver. If memory allocation fails, the driver could dereference a NULL pointer instead of handling the failure cleanly. The public record does not provide a CVSS score, impact rating, or exploitation evidence, so urgency should be based on Bluetooth exposure and kernel update cadence.

Executive priority

Treat this as a kernel hygiene item unless Bluetooth-dependent systems are business-critical. There is no sourced evidence of exploitation or severity scoring, but affected kernels should still be updated through normal vendor patch processes.

Technical view

CVE-2025-38641 is a resolved NULL pointer dereference flaw in Linux btusb error handling after kmalloc failure. The CVE record identifies affected Linux kernel versions around 6.16 through before 6.17 and references stable kernel commits that add proper allocation-failure handling.

Likely exposure

Exposure is most relevant to Linux systems using affected kernel builds with Bluetooth USB support. Systems without Bluetooth hardware, btusb usage, or affected kernel versions are less likely to be exposed, based on the provided record.

Exploitation context

The provided sources do not state active exploitation, public exploit availability, remote reachability, privileges required, or denial-of-service scope. CISA KEV status is false in the bundle, so active exploitation should not be assumed.

Researcher notes

Evidence is limited to the CVE description and two Linux stable commits. The bundle does not identify a CVSS vector, CWE, trigger conditions, attack prerequisites, or practical impact beyond potential NULL dereference on kmalloc failure.

Mitigation direction

  • Check distribution advisories for kernel packages addressing CVE-2025-38641.
  • Update to a vendor kernel containing the referenced stable btusb fixes.
  • Prioritize systems with Bluetooth USB hardware or enabled Bluetooth services.
  • Avoid relying on unsupported custom kernels without confirming the fix is included.

Validation and detection

  • Inventory Linux kernel versions across managed hosts.
  • Identify systems using Bluetooth USB hardware or the btusb driver.
  • Confirm whether installed kernel sources include the referenced stable commits.
  • Review vendor security advisories for affected and fixed package versions.
  • Check crash telemetry for Bluetooth-related NULL dereference events.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38641 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7d70989fcea7f79afe018a7e34d3486406c7a94e, 7d70989fcea7f79afe018a7e34d3486406c7a94eunaffected
LinuxLinux6.16, 0, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.