LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21937: Bluetooth: Add check for mgmt_alloc_skb() in mgmt_remote_name()

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Add check for mgmt_alloc_skb() in mgmt_remote_name() Add check for the return value of mgmt_alloc_skb() in mgmt_remote_name() to prevent null pointer dereference.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-21937 is a Linux kernel Bluetooth flaw that can crash affected systems through a null pointer dereference. The business impact is availability, not data theft. The source bundle rates it medium with CVSS 5.5, requiring local access and low privileges. No provided source shows active exploitation.

Executive priority

Address through normal kernel patch management, with higher priority for multi-user endpoints or systems where local denial of service affects operations. This is not presented as a remote compromise or data exposure issue in the provided sources.

Technical view

The issue is CWE-476 in the Linux Bluetooth management path. mgmt_remote_name() did not check whether mgmt_alloc_skb() returned null, allowing a kernel null pointer dereference. The CVSS vector is local, low complexity, low privileges, no user interaction, with high availability impact only.

Likely exposure

Exposure is most relevant for Linux systems running source-listed affected kernel versions with Bluetooth management functionality available. Servers without Bluetooth hardware or disabled Bluetooth services are likely less exposed, but kernel package status should still be checked against vendor advisories.

Exploitation context

The CVSS vector indicates local exploitation with low privileges and no user interaction. The provided data does not include exploit availability, in-the-wild use, or KEV listing. Treat this as a denial-of-service risk unless vendor guidance adds more detail.

Researcher notes

Evidence supports a kernel availability bug fixed by adding an allocation-failure check. Affected-version detail in the bundle is limited to CVE records and stable commit references; use distribution advisories for precise package mapping. Do not infer remote reachability from Bluetooth involvement alone.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Apply Debian LTS or distribution kernel updates where applicable.
  • Disable or restrict Bluetooth where it is unnecessary.
  • Check vendor advisories for exact fixed package versions.
  • Prioritize shared, desktop, kiosk, and exposed Linux endpoints.

Validation and detection

  • Inventory Linux kernel versions across managed systems.
  • Confirm Bluetooth support or services are present where risk matters.
  • Map installed kernels to distribution security advisories.
  • Verify patched kernels include the referenced stable commits.
  • Review crash logs for Bluetooth-related null dereference events.
Prepared
Confidence
high
Sources
8

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.

cwe · low confidence lookup

CWE-476: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-21937 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2025-21937Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxba17bb62ce415950753c19d16bb43b2bd3701158, ba17bb62ce415950753c19d16bb43b2bd3701158, ba17bb62ce415950753c19d16bb43b2bd3701158, ba17bb62ce415950753c19d16bb43b2bd3701158, ba17bb62ce415950753c19d16bb43b2bd3701158, 0f526a6d3e9347d94c2c0b5292a3cb3b25115019, 5.17.2unaffected
LinuxLinux5.18, 0, 6.1.131, 6.6.83, 6.12.19, 6.13.7, 6.14affected
Weakness

CWE details

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

CWE-476 · source CWE mapping

NULL Pointer Dereference

NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.