Based on the description, a race condition in the Linux kernel’s Bluetooth RFCOMM implementation allows a hostile peer to close a listener socket while an accept request is in flight. This results in a use‑after‑free that can corrupt kernel memory and may lead to privilege escalation, arbitrary code execution, or denial of service. The likely attack vector is an attacker establishing a remote Bluetooth connection and initiating an RFCOMM session during the race. The weakness is a classic use‑after‑free fault (CWE‑416).

All Linux kernel installations that have not applied the current patch for CVE‑2026‑53256 are affected. No specific kernel version list is available in the CVE data, so any kernel that implements the RFCOMM participant socket list can be impacted unless the fix has already been merged.

The likely attack vector involves an attacker establishing an active Bluetooth connection to the vulnerable device and attempting to initiate an RFCOMM connection while simultaneously sending a close command to a listener socket. The exploit requires an active Bluetooth connection and the ability to initiate an RFCOMM connection while a peer cancels a listening socket. No EPSS or KEV data is available, and a CVSS score is not supplied, so the exact likelihood of exploitation in the wild is unknown. However, use‑after‑free bugs in kernel code are generally considered high severity, and the lack of a publicly available exploit does not eliminate the risk of an attacker discovering or crafting one.