LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31772: Bluetooth: hci_sync: fix stack buffer overflow in hci_le_big_create_sync

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: fix stack buffer overflow in hci_le_big_create_sync hci_le_big_create_sync() uses DEFINE_FLEX to allocate a struct hci_cp_le_big_create_sync on the stack with room for 0x11 (17) BIS entries. However, conn->num_bis can hold up to HCI_MAX_ISO_BIS (31) entries โ€” validated against ISO_MAX_NUM_BIS (0x1f) in the caller hci_conn_big_create_sync(). When conn->num_bis is between 18 and 31, the memcpy that copies conn->bis into cp->bis writes up to 14 bytes past the stack buffer, corrupting adjacent stack memory. This is trivially reproducible: binding an ISO socket with bc_num_bis = ISO_MAX_NUM_BIS (31) and calling listen() will eventually trigger hci_le_big_create_sync() from the HCI command sync worker, causing a KASAN-detectable stack-out-of-bounds write: BUG: KASAN: stack-out-of-bounds in hci_le_big_create_sync+0x256/0x3b0 Write of size 31 at addr ffffc90000487b48 by task kworker/u9:0/71 Fix this by changing the DEFINE_FLEX count from the incorrect 0x11 to HCI_MAX_ISO_BIS, which matches the maximum number of BIS entries that conn->bis can actually carry.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A local, low-privileged user can trigger a Linux Bluetooth flaw that overwrites kernel stack memory. Successful exploitation could crash the system or potentially compromise kernel confidentiality and integrity. Exposure depends on the affected kernel code and Bluetooth ISO functionality being available.

Executive priority

Treat as a high-priority local privilege and availability risk. Accelerate remediation on systems with Bluetooth capability and untrusted local users; validate vendor backports before declaring exposure based solely on version numbers.

Technical view

The Bluetooth hci_le_big_create_sync function allocated stack space for 17 BIS entries while accepting up to 31. Copying 18โ€“31 entries could overwrite adjacent stack memory by up to 14 bytes. The published fix sizes the flexible array using HCI_MAX_ISO_BIS.

Likely exposure

Linux systems running affected or unpatched vendor kernels are potentially exposed when Bluetooth ISO/BIS functionality is available to a local low-privileged user. The supplied version data is complex; distribution backports may make version-only assessment unreliable.

Exploitation context

The CVSS vector indicates local access, low complexity, low privileges, and no user interaction, with potentially high system impact. The issue is described as trivially reproducible under KASAN, but the bundle reports no KEV listing or evidence of active exploitation.

Researcher notes

The overwrite occurs in an HCI command synchronization worker after a BIS count accepted up to ISO_MAX_NUM_BIS reaches a stack allocation sized for 17 entries. The bundle demonstrates memory corruption but does not establish reliable code execution, exploitation in the wild, or a non-patch workaround.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable upstream stable fix.
  • Check distribution security guidance for backports affecting your exact kernel build.
  • Prioritize shared, multi-user, kiosk, and endpoint systems where untrusted local access is possible.
  • Apply vendor-recommended temporary mitigations if patching cannot occur promptly.

Validation and detection

  • Record exact kernel package versions and distribution build identifiers across Linux assets.
  • Confirm whether each kernel includes the applicable stable fix or vendor backport.
  • Identify systems exposing Bluetooth ISO functionality to untrusted local users.
  • After updating, verify the corrected kernel is running following any required reboot.
  • Review security and crash telemetry for Bluetooth-related kernel memory faults.
Prepared
Confidence
high
Sources
6

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-2026-31772 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
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

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.

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

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-31772Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
LinuxLinux91d19383b7ed035e22165ae5c836e50bb9f95fbe, 42ecf1947135110ea08abeaca39741636f9a2285, 42ecf1947135110ea08abeaca39741636f9a2285, 42ecf1947135110ea08abeaca39741636f9a2285, 8958e1cee4e2eac1a5b825caa4dd96ce9ed975dd, 6.12.2, 6.11.11unaffected
LinuxLinux6.13, 0, 6.12.81, 6.18.22, 6.19.12, 7.0affected
Weakness

CWE details

No CWE listed

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