Security readout for executives and security teams
Plain-English summary
A race in the Linux Bluetooth connection process can make the kernel use memory after it has been freed. The supplied CVSS vector indicates a nearby, unauthenticated attack path with potentially severe confidentiality, integrity, and availability impact. The sources establish the bug and upstream fixes, but not real-world exploitation or practical exploitability.
Executive priority
Prioritize expedited assessment and patching for Bluetooth-capable Linux endpoints operating near untrusted people. Immediate emergency response is not supported by current exploitation evidence, but the high score and kernel memory-safety impact justify prompt action. Systems without enabled or usable Bluetooth are lower priority pending verification.
Technical view
During pending ACL or LE connection creation, a connection object in BT_OPEN state may be freed by concurrent HCI event handling while command work still references it. KASAN observed a two-byte write-after-free in hci_acl_create_conn_sync on Linux 6.16-rc7. Referenced stable commits correct the affected connection paths.
Likely exposure
Exposure is most plausible on Linux systems running an affected or unpatched backported kernel with Bluetooth available and connection or pairing activity possible. The supplied affected-version data is flattened and ambiguous, so upstream version numbers alone are insufficient. Distribution package status, Bluetooth availability, and inclusion of a referenced fix should determine exposure.
Exploitation context
The CVSS 3.1 vector rates this 8.8 with adjacent access, low complexity, no privileges, and no user interaction. However, the bundle marks KEV false and cites no active exploitation, public proof of concept, or confirmed impact beyond the KASAN report. Treat severe compromise as scoring-based potential, not demonstrated exploitation.
Researcher notes
The trace shows allocation during device pairing, concurrent deletion in HCI connection-complete handling, and a later write from synchronous command work. The report extends the correction to analogous LE connection creation. The bundle does not specify triggering radio traffic, reliability, or whether practical exploitation can control the freed object.
Mitigation direction
- Install a vendor-supported kernel containing the applicable upstream fix, then reboot into that kernel.
- Until patched, disable Bluetooth where it is unnecessary or exposed to untrusted nearby devices.
- Check distribution guidance for backports because package versions may not match upstream kernel version boundaries.
- Prioritize Bluetooth-capable systems operating in public or otherwise untrusted physical environments.
Validation and detection
- Verify the running kernel and distribution package against vendor guidance and the CVE record.
- Confirm the installed kernel contains a referenced stable fix or an equivalent vendor backport.
- Inventory systems with Bluetooth hardware, drivers, and services enabled.
- After updating and rebooting, confirm the expected kernel is active and Bluetooth functionality remains operational.
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-39982 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
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/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:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:A/AC:L/PR:N/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/6243bda271a628c48875e3e473206e7f584892ceCVE reference, Linux
- https://git.kernel.org/stable/c/bcce99f613163a43de24674b717e7a6c135fc879CVE reference, Linux
- https://git.kernel.org/stable/c/484c7d571a3d1b3fd298fa691b660438c4548a53CVE reference, Linux
- https://git.kernel.org/stable/c/a78fd4fc5694ecb3b97deb2ad9eaebd67b4d2b08CVE reference, Linux
- https://git.kernel.org/stable/c/9e622804d57e2d08f0271200606bd1270f75126fCVE 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.