LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31511: Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete This fixes the condition checking so mgmt_pending_valid is executed whenever status != -ECANCELED otherwise calling mgmt_pending_free(cmd) would kfree(cmd) without unlinking it from the list first, leaving a dangling pointer. Any subsequent list traversal (e.g., mgmt_pending_foreach during __mgmt_power_off, or another mgmt_pending_valid call) would dereference freed memory.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux kernel’s Bluetooth management code can leave a reference to freed memory. A locally authenticated, low-privilege attacker could potentially trigger memory corruption, causing system compromise or disruption. The supplied CVSS score is 7.8, but exposure depends on the deployed kernel, Bluetooth functionality, and vendor backports.

Executive priority

Treat as a high-priority kernel update for exposed endpoints and systems permitting untrusted local users. It is less urgent for systems without relevant Bluetooth functionality or local-user exposure, but inventory and vendor verification should occur promptly because successful exploitation could affect all three security objectives.

Technical view

An incorrect completion-path condition can free a pending Bluetooth management command without first unlinking it. Later traversal of the pending-command list can dereference that freed object, creating a kernel use-after-free condition. The supplied vector indicates local access, low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact.

Likely exposure

Potentially exposed assets are Linux systems running an affected or unfixed kernel with relevant Bluetooth management functionality available. The supplied version data includes unusual entries and commit identifiers, so version strings alone are insufficient. Distribution kernels may contain backported fixes without matching upstream version numbers.

Exploitation context

The supplied record does not establish active exploitation, and the CVE is not marked as present in KEV. Exploitation requires local, low-privilege access according to the supplied CVSS vector. No public proof-of-concept or confirmed attack activity is identified in the provided sources.

Researcher notes

The described defect is a dangling-list-entry use-after-free in mgmt_add_adv_patterns_monitor_complete. Subsequent mgmt_pending_foreach or mgmt_pending_valid traversal provides the dereference path. The source bundle identifies several stable-tree commits, but does not clearly map every affected branch or identify a single introducing commit; confirm ancestry and backport status per kernel build.

Mitigation direction

  • Apply a vendor-supported kernel update containing the relevant upstream fix or backport.
  • Check distribution advisories because package versions may not align with upstream kernel versions.
  • Prioritize shared, multi-user, kiosk, desktop, and Bluetooth-enabled Linux systems.
  • Where patching is delayed, restrict untrusted local access and review whether Bluetooth is operationally required.

Validation and detection

  • Record each system’s running kernel and distribution package version.
  • Confirm the vendor package changelog or advisory explicitly addresses CVE-2026-31511.
  • Compare custom kernels against the cited stable fix commits or verified backports.
  • Reboot after updating and confirm the patched kernel is running.
  • Review kernel logs for Bluetooth-related use-after-free, crashes, or memory-corruption indicators.
Prepared
Confidence
high
Sources
7

Public sources used

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-31511 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
6Source 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-31511Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a, d71b98f253b079cbadc83266383f26fe7e9e103b, 302a1f674c00dd5581ab8e493ef44767c5101aab, 302a1f674c00dd5581ab8e493ef44767c5101aab, 302a1f674c00dd5581ab8e493ef44767c5101aab, 87a1f16f07c6c43771754075e08f45b41d237421, 6.12.59, 6.16.10unaffected
LinuxLinux6.17, 0, 6.12.80, 6.18.21, 6.19.11, 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.