CVSS 3.1
8.8 highCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HHigh (8.8) in linux linux. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2023-53827 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-53827?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-53827?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-53827 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 3.5 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 4.14 | 4.14.313 |
| Linux | 4.19 | 4.19.281 |
| Linux | 5.4 | 5.4.241 |
| Linux | 5.10 | 5.10.178 |
| Linux | 5.15 | 5.15.108 |
| Linux | 6.1 | 6.1.25 |
| Linux | 6.2 | 6.2.12 |
| Linux | later releases | 6.3 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | linux | 6.1.25-1 | DEBIAN-CVE-2023-53827 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2023-53827 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2023-53827 |
| Ubuntu | 20.04:LTS | linux | 5.4.0-156.173 | UBUNTU-CVE-2023-53827 |
| Ubuntu | 20.04:LTS | linux-aws | 5.4.0-1107.115 | UBUNTU-CVE-2023-53827 |
| Ubuntu | 20.04:LTS | linux-aws-5.15 | 5.15.0-1041.46~20.04.1 | UBUNTU-CVE-2023-53827 |
| Ubuntu | 20.04:LTS | linux-azure | 5.4.0-1114.120 | UBUNTU-CVE-2023-53827 |
| Ubuntu | 20.04:LTS | linux-azure-5.15 | 5.15.0-1045.52~20.04.1 | UBUNTU-CVE-2023-53827 |
| Ubuntu | 20.04:LTS | linux-bluefield | 5.4.0-1068.74 | UBUNTU-CVE-2023-53827 |
| Ubuntu | 20.04:LTS | linux-gcp | 5.4.0-1110.119 | UBUNTU-CVE-2023-53827 |
| Ubuntu | 20.04:LTS | linux-gcp-5.15 | 5.15.0-1039.47~20.04.1 | UBUNTU-CVE-2023-53827 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2023-53827 |
| Ubuntu | 20.04:LTS | linux-hwe-5.15 | 5.15.0-79.86~20.04.2 | UBUNTU-CVE-2023-53827 |
| 48 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Red Hat | rhel_aus:8.2::baseos | perf, kernel, bpftool and 21 more | 0:4.18.0-193.187.1.el8_2 | RHSA-2026:3388 |
| Red Hat | rhel_aus:8.4::baseos, rhel_eus_long_life:8.4::baseos | perf, kernel, bpftool and 21 more | 0:4.18.0-305.186.1.el8_4 | RHSA-2026:3360 |
| SUSE | Linux Enterprise High Availability Extension 15 SP4, Linux Enterprise Live Patching 15 SP4, Linux Enterprise Micro 5.3 and 1 more | kernel-default | 5.14.21-150400.24.194.1 | SUSE-SU-2026:0617-1 |
| SUSE | Linux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS | kernel-64kb, kernel-docs, kernel-syms and 3 more | 5.14.21-150400.24.194.1 | SUSE-SU-2026:0617-1 |
| SUSE | Linux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Micro 5.3 and 3 more | kernel-default-base | 5.14.21-150400.24.194.1.150400.24.98.3 | SUSE-SU-2026:0617-1 |
| SUSE | Linux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS | kernel-64kb, kernel-docs, kernel-syms and 3 more | 5.14.21-150500.55.133.1 | SUSE-SU-2026:0317-1 |
| SUSE | Linux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Micro 5.5 and 2 more | kernel-default-base | 5.14.21-150500.55.133.1.150500.6.65.1 | SUSE-SU-2026:0317-1 |
| SUSE | Linux Enterprise Live Patching 12 SP5 | kernel-default | 4.12.14-122.296.1 | SUSE-SU-2026:1078-1 |
| SUSE | Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_78 | 1-8.3.1 | SUSE-SU-2026:1078-1 |
| SUSE | Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_48 | 1-150400.9.7.1 | SUSE-SU-2026:0617-1 |
| SUSE | Linux Enterprise Live Patching 15 SP5 | kernel-default | 5.14.21-150500.55.133.1 | SUSE-SU-2026:0317-1 |
| SUSE | Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_34 | 1-150500.11.3.1 | SUSE-SU-2026:0317-1 |
| SUSE | Linux Enterprise Micro 5.2 | kernel-default | 5.3.18-150300.59.238.1 | SUSE-SU-2026:0928-1 |
| SUSE | Linux Enterprise Micro 5.2 | kernel-default-base | 5.3.18-150300.59.238.1.150300.18.142.1 | SUSE-SU-2026:0928-1 |
| 9 more for SUSE in the JSON and on SUSE's page. | ||||
| Alpaquita | stream | linux-lts | 6.6.58-r0 | BELL-CVE-2023-53827 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · Alpaquita.
Red Hat rates this Moderate.
A race in the L2CAP disconnect request/response handlers could access a channel that is being destroyed, causing a use-after-free and kernel crash. The fix uses l2cap_chan_hold_unless_zero() and proper locking around channel deletion to avoid referencing freed objects. An adjacent attacker over Bluetooth can trigger this during disconnect handling on an active link. Likely only denial-of-service kind of attack possible, but cannot prove this.
The complexity of attack is high, because it requires a precise race condition between the local channel teardown (triggered by the kernel) and a crafted L2CAP_DisconnectReq or L2CAP_DisconnectRsp message sent by the remote peer at exactly the same time. The timing window is very narrow — the attacker must send or respond to the disconnect while the kernel is already in the process of releasing the l2cap_chan structure but before the reference count reaches zero. Achieving this reliably would require repeated connect/disconnect cycles or fuzzing at the signaling layer, making stable exploitation unlikely outside of a controlled test setup.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 8.2 Advanced Update Support | kernel-0:4.18.0-193.187.1.el8_2 | Fixed 2026-02-26 | RHSA-2026:3388 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | kernel-0:4.18.0-305.186.1.el8_4 | Fixed 2026-02-25 | RHSA-2026:3360 |
| Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On | kernel-0:4.18.0-305.186.1.el8_4 | Fixed 2026-02-25 | RHSA-2026:3360 |
| Red Hat Enterprise Linux 10 | kernel | Not affected | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Out of support scope | |
| Red Hat Enterprise Linux 7 | kernel-rt | Out of support scope | |
| Red Hat Enterprise Linux 8 | kernel | Affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Affected | |
| Red Hat Enterprise Linux 9 | kernel | Not affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-53827.