Bug 2025034 (CVE-2021-41229) - CVE-2021-41229 bluez: memory leak in the SDP protocol
Summary: CVE-2021-41229 bluez: memory leak in the SDP protocol
Keywords:
Status: NEW
Alias: CVE-2021-41229
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2027434 2027435 2025035
Blocks: 2025036
TreeView+ depends on / blocked
 
Reported: 2021-11-19 18:27 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-11-29 16:21 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2021-11-19 18:27:47 UTC
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.

Reference:
https://github.com/bluez/bluez/security/advisories/GHSA-3fqg-r8j5-f5xq

Comment 1 Guilherme de Almeida Suckevicz 2021-11-19 18:28:02 UTC
Created bluez tracking bugs for this issue:

Affects: fedora-all [bug 2025035]

Comment 2 Garrett Tucker 2021-11-29 16:20:45 UTC
All versions of RHEL are affected by this flaw. This is low in impact however so flaw remediation will be delegated for supported releases. The flaw was caused by unfreed memory of a linked list which led to a memory leak. This could become very large which could result in the service crashing due to this flaw. A patch has been applied by ubuntu for all bluez packages and link provided below: 

Patch: https://git.launchpad.net/ubuntu/+source/bluez/diff/debian/patches/CVE-2021-41229.patch?h=applied/ubuntu/hirsute-security


Note You need to log in before you can comment on or make changes to this bug.