LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21936: Bluetooth: Add check for mgmt_alloc_skb() in mgmt_device_connected()

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

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel Bluetooth flaw that can crash affected systems through a null pointer dereference. It is primarily an availability risk, not a data theft or privilege escalation issue based on the supplied CVSS vector. Exploitation requires local access with low privileges, so prioritize exposed multi-user Linux systems and endpoints where Bluetooth is enabled.

Executive priority

Treat as a routine but real availability patch. It is not currently evidenced as exploited and does not indicate data compromise, but kernel crashes can disrupt business services. Include it in the next kernel maintenance cycle, faster for shared Linux systems with local users.

Technical view

The kernel Bluetooth management path mgmt_device_connected() did not check whether mgmt_alloc_skb() returned null. The upstream resolution adds that check to prevent a null pointer dereference. The CVSS vector is local, low complexity, low privileges, no user interaction, unchanged scope, and high availability impact only.

Likely exposure

Affected exposure is limited to Linux kernels identified by the CVE data and downstream distributions carrying vulnerable Bluetooth code. Systems without Bluetooth use or without local untrusted users are lower priority, but still need normal kernel patch management.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. The CVSS vector indicates local, low-privilege exploitation with no user interaction and high availability impact. No public exploit status is established by the provided evidence.

Researcher notes

Focus analysis on the Bluetooth management code path and vendor backport status. The affected-version data in the bundle is sparse and somewhat irregular, so rely on distro advisories and kernel package metadata for final exposure decisions. Do not infer remote attackability from the Bluetooth component alone.

Mitigation direction

  • Apply vendor kernel updates that include the referenced upstream stable fixes.
  • For Debian LTS systems, review and follow the cited Debian LTS advisory.
  • Prioritize multi-user Linux systems and endpoints where Bluetooth is enabled.
  • If no vendor package is available, monitor vendor guidance for supported backports.
  • Avoid direct deployment shortcuts; use normal tested kernel update processes.

Validation and detection

  • Inventory Linux hosts and record running kernel versions and distribution packages.
  • Check vendor advisories or changelogs for CVE-2025-21936 coverage.
  • Confirm patched kernels include the applicable upstream stable fix or vendor backport.
  • Review whether Bluetooth is enabled on systems pending patching.
  • Regression-test critical workloads after kernel updates before broad rollout.
Prepared
Confidence
medium
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-21936 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-21936Attack 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
LinuxLinuxe96741437ef0a5d18144e790ac894397efda0924, e96741437ef0a5d18144e790ac894397efda0924, e96741437ef0a5d18144e790ac894397efda0924, e96741437ef0a5d18144e790ac894397efda0924, e96741437ef0a5d18144e790ac894397efda0924unaffected
LinuxLinux5.17, 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.