CVE-2026-53256

Description

A flaw was found in the Linux kernel's Bluetooth RFCOMM (Radio Frequency Communication) subsystem. A race condition in the rfcomm_connect_ind() function, specifically during the handling of listener sockets, can lead to a use-after-free vulnerability. A local attacker could exploit this to cause a denial of service or potentially achieve arbitrary code execution.

Statement

A race in Bluetooth RFCOMM can leave rfcomm_connect_ind using a listener socket after it was closed and freed by another path. The selected listener was returned after dropping rfcomm_sk_list.lock without holding a reference, so close can unlink and free the parent before lock_sock, bt_accept_enqueue, or the deferred setup callback uses it. KASAN reported a slab use after free in lock_sock_nested, which makes this a memory safety issue rather than a pure DoS only bug. For the CVSS the PR:N is used for the paranoid score because an adjacent Bluetooth peer may trigger connection indications without local privileges on the victim, assuming a reachable RFCOMM listener and suitable Bluetooth access. The issue is not Internet reachable and should be treated as AV:A because exploitation requires Bluetooth proximity or access to the local Bluetooth network.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.5N/A8
Attack VectorAdjacent NetworkN/AAdjacent Network
Attack ComplexityHighN/ALow
Privileges RequiredNoneN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

cve.org: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.