CVE-2023-53827

8.8 HIGH 0.4% exploit odds No fix listed Memory safety OS & kernel

What it is

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.

At a glance

Exploitability: Can be exploited from the same network segment without logging in. High risk of data exposure, data tampering, service disruption.
Exploit odds: 0.4% chance of exploitation in the next 30 days (EPSS).
Fix: No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

2025-12-09 01:27 UTC ReservedThe CVE id was reserved by its CNA
2025-12-09 16:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-10-15 22:17 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.4% in the next 30 days (EPSS).
Severity: 8.8 HIGH (CVSS).
Fix: none linked yet, which raises it.

Details

Published: 2025-12-09 16:17 UTC
Last modified: 2026-10-15 22:17 UTC
Exploit probability: 0.4% · EPSS, next 30 days
Record status: Deferred

Attack profile CVSS 3.1 · 8.8

Attack vector: Adjacent network
Complexity: Low
Privileges needed: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Raw vector

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

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2023-53827.md and follow it. Check whether this project is affected by CVE-2023-53827. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

References

NVD record · CVE.org record