Security readout for executives and security teams
Plain-English summary
A race condition in the Linux kernel’s Bluetooth management code can access memory after it has been freed. The documented result is a kernel crash; the CVSS assessment also allows possible confidentiality and integrity impact. Exploitation requires local, low-privileged access, reducing internet-facing risk but making shared or multi-user Linux systems more concerning.
Executive priority
Treat this as a high-priority kernel patching item, especially for shared or Bluetooth-enabled endpoints. It is not supported as an internet-remote or actively exploited emergency by the supplied evidence. Use accelerated routine remediation, validate actual kernel packages, and avoid relying solely on the ambiguous version list.
Technical view
Concurrent access to the Bluetooth mgmt_pending list can trigger a slab use-after-free in hci_sock_get_channel through management-command processing. The kernel fix adds dedicated mutex protection around the list. The supplied KASAN trace demonstrates the memory-safety failure on arm64 under syzkaller testing; it does not demonstrate real-world compromise.
Likely exposure
Exposure is most likely on affected Linux systems where Bluetooth management functionality is available to a local low-privileged user. The supplied affected-version data is ambiguous and should not be treated as complete release boundaries. Confirm applicability using the running distribution’s kernel package and whether it includes a referenced stable fix.
Exploitation context
The supplied CVSS 3.1 score is 7.8 with local access, low complexity, low privileges, and no user interaction. The CVE is not listed as KEV in the bundle, and no source provided here establishes active exploitation or a public weaponized exploit. The evidence documents a syzkaller-triggered crash and use-after-free.
Researcher notes
The crash path involves mgmt_pending_find during Bluetooth management command handling, with concurrent allocation and freeing producing a slab use-after-free. Referenced stable commits provide the authoritative fix lineage. Exact vulnerable version ranges, exploitability beyond denial of service, architecture breadth, and practical privilege boundaries are not fully established by the supplied bundle.
Mitigation direction
- Install a vendor-supported kernel update containing the applicable stable fix commit.
- Map distribution kernel packages to the referenced upstream fixes before declaring systems remediated.
- Prioritize shared, multi-user, desktop, and Bluetooth-enabled systems for patching.
- If patching is delayed, consult vendor guidance for supported Bluetooth exposure-reduction measures.
Validation and detection
- Inventory running kernel versions and distribution package revisions across Linux assets.
- Confirm whether each kernel package contains an applicable referenced stable fix.
- Identify systems exposing Bluetooth management functionality to local unprivileged users.
- Review kernel logs for Bluetooth-related KASAN, use-after-free, or unexpected crash indicators.
- Reboot after kernel updates and verify the remediated kernel is running.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2025-38117 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/7b5958332f20dc66b19be564c402dbc21b927a81CVE reference, Linux
- https://git.kernel.org/stable/c/bdd56875c6926d8009914f427df71797693e90d4CVE reference, Linux
- https://git.kernel.org/stable/c/4e83f2dbb2bf677e614109df24426c4dded472d4CVE reference, Linux
- https://git.kernel.org/stable/c/d7882db79135c829a922daf3571f33ea1e056ae3CVE reference, Linux
- https://git.kernel.org/stable/c/6fe26f694c824b8a4dbf50c635bee1302e3f099cCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.