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