LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41229: Memory leak in BlueZ

BlueZ is a Bluetooth protocol stack for Linux. In affected versions a vulnerability exists in sdp_cstate_alloc_buf which allocates memory which will always be hung in the singly linked list of cstates and will not be freed. This will cause a memory leak over time. The data can be a very large object, which can be caused by an attacker continuously sending sdp packets and this may cause the service of the target device to crash.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-41229 is a BlueZ Bluetooth stack memory leak. A nearby attacker could repeatedly interact with SDP handling and make the target service consume memory until it crashes. This is mainly an availability issue, not a data theft or privilege escalation issue.

Executive priority

Treat this as a moderate availability risk. Prioritize patching for Bluetooth-enabled servers, kiosks, appliances, industrial endpoints, and mobile Linux devices where service crashes could affect operations. Lower priority applies where Bluetooth is disabled or physically inaccessible.

Technical view

Affected BlueZ 5.58 leaks memory in sdp_cstate_alloc_buf because allocated buffers remain attached to the cstates singly linked list and are not freed. Large repeated SDP traffic can grow memory use over time and crash the service. CVSS 3.1 is 4.3, AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.

Likely exposure

Exposure is most likely on Linux or embedded systems running BlueZ 5.58 with Bluetooth enabled and SDP reachable from nearby Bluetooth range. NetApp and Debian advisories show downstream ecosystem relevance, but the source bundle does not identify specific NetApp products or every affected distribution package.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires adjacent Bluetooth reachability, no privileges, and no user interaction. The practical impact is service instability or crash through memory exhaustion, not confidentiality or integrity compromise.

Researcher notes

The available evidence supports a resource-consumption flaw in BlueZ 5.58 with adjacent-network attack vector. The bundle does not provide exploit status, fixed upstream version, or complete downstream product mapping, so validation should rely on vendor package advisories and local version inventory.

Mitigation direction

  • Identify systems running BlueZ 5.58 or vendor packages derived from it.
  • Apply BlueZ security updates from the operating system or appliance vendor.
  • Disable Bluetooth where it is not operationally required.
  • Restrict physical and radio proximity to sensitive Bluetooth-enabled assets.
  • Review Debian, NetApp, and vendor advisories for product-specific guidance.

Validation and detection

  • Inventory Linux, appliance, and embedded assets that include BlueZ.
  • Confirm installed BlueZ package versions against vendor security advisories.
  • Verify whether Bluetooth and SDP services are enabled on exposed devices.
  • Check service logs for unexplained Bluetooth crashes or memory pressure.
  • Confirm updated packages are deployed through normal patch compliance evidence.
Prepared
Confidence
high
Sources
7

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-400: 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-2021-41229 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
4.3 (3.1)
Known Exploited
No
Published

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

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
0Timeline 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
4.3CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2021-41229Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
bluezbluez= 5.58Listed
Weakness

CWE details

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

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.