VYPR
Unrated severityNVD Advisory· Published Dec 9, 2025· Updated Apr 15, 2026

CVE-2023-53827

CVE-2023-53827

Description

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp}

Similar to commit d0be8347c623 ("Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put"), just use l2cap_chan_hold_unless_zero to prevent referencing a channel that is about to be destroyed.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A use-after-free vulnerability in the Linux kernel's Bluetooth L2CAP subsystem can be triggered during disconnect requests, potentially leading to a crash or code execution.

Vulnerability

Description

A use-after-free vulnerability exists in the Linux kernel's Bluetooth L2CAP implementation, specifically in the l2cap_disconnect_req and l2cap_disconnect_rsp functions. The root cause is that the code could reference a channel that is about to be destroyed without properly holding a reference to it, leading to a use-after-free condition. This is similar to a previously fixed issue in commit d0be8347c623 ("Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put") [1].

Exploitation

The vulnerability can be exploited by an attacker who is able to send crafted Bluetooth L2CAP disconnect requests or responses to a target system. The attack requires Bluetooth communication capabilities. The attack does not require authentication, as it can be triggered by an unauthenticated remote attacker within Bluetooth range. The flaw is in the handling of channel references during the disconnect procedure, where the code fails to use l2cap_chan_hold_unless_zero to prevent accessing a channel that is being freed [1].

Impact

Successful exploitation could lead to a denial of service (system crash) or potentially allow an attacker to execute arbitrary code in the context of the kernel. The use-after-free condition can corrupt kernel memory, which may be leveraged for privilege escalation or other malicious purposes.

Mitigation

The vulnerability has been patched in the Linux kernel. The fix involves using l2cap_chan_hold_unless_zero to ensure that a reference is held before accessing the channel, preventing the use-after-free. Users should apply the latest stable kernel updates to address this issue [1].

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2
  • Linux/Kernelinferred2 versions
    (expand)+ 1 more
    • (no CPE)
    • (no CPE)

Patches

8

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

8

News mentions

0

No linked articles in our index yet.